This fix makes a fixture with no tests (and no setup/teardown errors)
succeed. NUnit 2.5.3 is returning Inconclusive in this case. It's really
not clear which is best so we'll leave things as they are for now. There
will be a review of the use of Inconclusive state at some point in NUnit
3.0 development and we'll resolve the issue then.
** Changed in: nunit-3.0
Status: Triaged => In Progress
** Changed in: nunit-3.0
Milestone: None => 2.9.4
--
Fixture With No Tests Shows as Non-Runnable
https://bugs.launchpad.net/bugs/419411
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
Status in NUnit Test Framework: In Progress
Status in NUnit V2 Test Framework: Fix Released
Bug description:
Fixtures with no tests are displayed as non-runnable, which is not strictly
true. Logically, it seems that they should be considered as inconclusive.
_______________________________________________
Mailing list: https://launchpad.net/~nunit-core
Post to : [email protected]
Unsubscribe : https://launchpad.net/~nunit-core
More help : https://help.launchpad.net/ListHelp
