This bug is now reflected in the following bugs on GitHub:
https://github.com/nunit/nunit-console/issues/4
https://github.com/nunit/nunit-gui/issues/17
https://github.com/nunit/nunit-gui/issues/18
and is being closed here as "wontfix"
** Changed in: nunit-console
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/881617
Title:
Tests with invalid category attributes should be more visible
Status in NUnit Console Runner:
Won't Fix
Status in NUnit V2 Test Framework:
Fix Released
Bug description:
When a test is marked with an invalid category attribute, like aaa-
bbb, that test is marked as not-runnable and shows up as an error in
both the gui and console if we try to run it. However, if we make the
mistake of asking nunit to run category aaa-bbb, then the test in
question is not run (because aaa-bbb is a valid category expression)
and no error appears. From the point of view of the user, the test
seems to have just disappeared.
The following changes are needed, at a minimum, to make it clearer to
the user just what is happening:
1. Not runnable tests should show as red in the gui as soon as the
tests are loaded, without waiting for a test run. They should remain
red even after a test run that does not include them.
2. Invalid categories should not be listed for selection by the gui at
all.
3. The console runner output should use wording that indicates aaa-bbb
is a category expression rather than a simple category.
See bug #881357 for more info on the motivation for this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-console/+bug/881617/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~nunit-core
Post to : nunit-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nunit-core
More help : https://help.launchpad.net/ListHelp
