How does (or should) the VS Addin deal with unit tests?

How does the VS Addin currently deal with unit tests?

Does it have a hard-coded value for a directory name that it "knows"
contains tests which are excluded from packaging?  (As discussed in
comments on [1].)

How does this compare to the command line?

The VS solutions I'm looking at are using a separate 'project' for the
tests.  Assuming NMaven and the Addin support "ignoring" a directory
containing tests, so that tests can be in the same module as the
project code, is that also supported somehow by VS?

I've opened NMAVEN-152 [2] to improve this, though I probably don't
have a complete understanding yet and it will need to be edited.

[1] http://docs.codehaus.org/display/MAVENUSER/NMaven+Project+Directory+Structure
[2] http://jira.codehaus.org/browse/NMAVEN-152

Thanks,
--
Wendy