incubator-nmaven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Stevens Ancajas" <>
Subject Re: How does (or should) the VS Addin deal with unit tests?
Date Thu, 26 Jun 2008 10:55:20 GMT
For the VS add-in it is hardcoded

On Wed, Jun 25, 2008 at 6:13 AM, Wendy Smoak <> wrote:

> 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?

For the VS addin  it knows the test directory through the pom which is
assumed that it is located side by side with the selected csproj file . If
the pom is not located there, it traverses 3 directories up (for the "2
csproj  1 pom.xml" setup, where the dir structure is assumed to be
"src\test\csharp" )

> 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]
> [2]
> Thanks,
> --
> Wendy

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message