nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Hi,

Bear in mind that NUnit has to do the same thing for any assemblies without
tests - both those you included deliberately in order to set the probing path
correctly and those you may have included erroneously. If we simply hid the
assemblies, then any included accidentally - for example Xxxx.dll when
Xxxx.Tests.dll was intended - would be hidden. In general, we want to avoid
hiding any errors even at the cost of some false negatives.

The tree nodes in question are colored red and marked with X because this is
the icon for a non-runnable test - also used for failures and errors.
It's the same
mark you get when a fixture has no valid constructor, for example. In
the specific
case of an assembly without tests, however, we don't reflect the error up to the
top level, which is why the bar stays green.

To avoid the issue entirely, you can set your probing path directly in the
ProjectEditor and not include the assembly.

One of the earlier versions of NUnit used an attribute in the project
file to indicate
that an assembly contained no tests. If there is support for it, we
could reinstate
this feature.

For now, I'm closing this bug using the new Launchpad status of "Opinion" to
indicate that further discussion is possible. I suggest you try out
the suggested
workaround and initiate a general discussion (on nunit-discuss) if
you'd like to
see the behavior changed anyway.

Charlie

On Thu, Jul 22, 2010 at 1:46 AM, Yodan Tauber <608596@xxxxxxxxxxxxxxxxxx> wrote:
> Public bug reported:
>
> I have an NUnit project file which specifies some assemblies. Some of
> these assemblies actually contain test fixtures and some do not. I need
> these test-less assemblies in the project because they are a dependency
> of some of my test assemblies (if I didn't include them explicitly in
> the project file, the framework wouldn't find the correct version of
> these assemblies).
>
> In the GUI runner, I select the root (project) node in the test tree and
> click "Run". Each assembly which doesn't have tests gets an "X" icon.
> The "final" status of NUnit is still a success, though (the progress bar
> stays green). I'm not sure what icon should be there instead - perhaps
> none at all (stay gray) - but this "X" definitely isn't the right choice
> (I think it's very confusing).
>
> Another (unrelated) idea would be to hide these assemblies from the tree
> altogether.
>
> Using NUnit GUI v2.5.5.10112
>
> ** Affects: nunitv2
>     Importance: Undecided
>         Status: New
>
> --
> Assemblies with no tests are marked with an X
> https://bugs.launchpad.net/bugs/608596
> You received this bug notification because you are a member of NUnit
> Developers, which is subscribed to NUnit V2.
>

** Changed in: nunitv2
       Status: New => Opinion

-- 
Assemblies with no tests are marked with an X
https://bugs.launchpad.net/bugs/608596
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.

Status in NUnit V2 Test Framework: Opinion

Bug description:
I have an NUnit project file which specifies some assemblies. Some of these assemblies actually contain test fixtures and some do not. I need these test-less assemblies in the project because they are a dependency of some of my test assemblies (if I didn't include them explicitly in the project file, the framework wouldn't find the correct version of these assemblies).

In the GUI runner, I select the root (project) node in the test tree and click "Run". Each assembly which doesn't have tests gets an "X" icon. The "final" status of NUnit is still a success, though (the progress bar stays green). I'm not sure what icon should be there instead - perhaps none at all (stay gray) - but this "X" definitely isn't the right choice (I think it's very confusing).

Another (unrelated) idea would be to hide these assemblies from the tree altogether.

Using NUnit GUI v2.5.5.10112