Such an assembly is not shown as a failure, but as "NotRunnable". This can be determined by right-clicking it in the test tree and selecting "Properties." We are aware that the Properties display is often not discovered by users from past bug reports on other issues so we are working on some way to make it more easily discoverable in the next major release.
I agree that there is a problem here, but I don't think that falsely showing the test as passing is a good solution. We consider putting a non-test assembly into the project as a user error of the same type as trying to run an abstract class or mismatching the arguments of a method. The problem I see is that there is no other info about the problem. It is not listed in either the Errors & Failures tab or the Tests not Run tab. It may also be an issue that we use the same icon for it as for a test failure. I'd like to re- target this bug toward improving how we display the problem, rather than redefining it as not a problem. For most users, an assembly with no tests is simply a mistake, but if the result is surprising we don't want them to spend an inordinate amount of time figuring it out. Feel free to comment further on the issue. I'm interested in knowing what process you use to generate new project files when you add a new assembly. Can't you simply filter out those with no tests at that point? Charlie On Tue, Feb 1, 2011 at 8:29 AM, simon misys <[email protected]> wrote: > Public bug reported: > > A test-free assembly is shown with the failure icon, ie, an X with red > background, in the GUI runner tree display, as is its parent(s). > > However, the progress bar is green, as expected (assuming all other > tests pass). > > Why would we want to include a test-free assembly? Because we want to > create a single NUnit project for an existing large solution (40+ Visual > Studio projects) containing all of its assemblies and executables. As > we progressively add new tests to our product, we want NUnit to > automatically pick them up without anyone having to remember to make > sure the corresponding assembly/executable have been added to the NUnit > project (and Debug/Release configurations). > > It is off-putting (to say the least) and misleading for NUnit label such > test-free assemblies as failures in the tree display. > It also contradicts what NUnit reports in the rest of the GUI (and when the > NUnit project is run with the console runner). > > So, I think NUnit should not show test-free assemblies as failures in > the tree display. I think they should count as a success, ie, shown > with a check with green background. > > Thanks. > > ** Affects: nunitv2 > Importance: Undecided > Status: New > > -- > You received this bug notification because you are a member of NUnit > Developers, which is subscribed to NUnit V2. > https://bugs.launchpad.net/bugs/711330 > > Title: > Test-free assembly given failure icon in tree display > -- You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. https://bugs.launchpad.net/bugs/711330 Title: Test-free assembly given failure icon in tree display Status in NUnit V2 Test Framework: New Bug description: A test-free assembly is shown with the failure icon, ie, an X with red background, in the GUI runner tree display, as is its parent(s). However, the progress bar is green, as expected (assuming all other tests pass). Why would we want to include a test-free assembly? Because we want to create a single NUnit project for an existing large solution (40+ Visual Studio projects) containing all of its assemblies and executables. As we progressively add new tests to our product, we want NUnit to automatically pick them up without anyone having to remember to make sure the corresponding assembly/executable have been added to the NUnit project (and Debug/Release configurations). It is off-putting (to say the least) and misleading for NUnit label such test-free assemblies as failures in the tree display. It also contradicts what NUnit reports in the rest of the GUI (and when the NUnit project is run with the console runner). So, I think NUnit should not show test-free assemblies as failures in the tree display. I think they should count as a success, ie, shown with a check with green background. Thanks. _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : [email protected] Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
