nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

By design, inconclusive results have no efffect on the overall passing or failing of the test run _unless_ a particular test type transforms the inconclusive result into something else. That's what Theories do, in fact. If _all_ the results under a Theory are inconclusive, then the
theory fails to be proven and shows up as red. Note that outside of theories, the only way to get an inconclusive result is to call Assert.Inconclusive.

OTOH, Ignoring a test is considered a "Bad Thing" - not as bad as a
failure, but pretty bad. For that reason it is highlighted in the bar.
That's not the same as Skipping a test, which is also neutral and
happens - for example - when a PlatformAttribute causes the test to be
excluded.

I'm closing this using the new "Opinion" status, which allows others to
continue to comment on it.

Best place to discuss possible changes to how we handle various test
results in the gui is on the nunit-discuss list.

** Changed in: nunit-3.0
       Status: New => Opinion

-- 
Wrong colors in testrunner? 
https://bugs.launchpad.net/bugs/605470
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: Opinion

Bug description:
In the testrunner, when a test is marked as Ignore the bar gets yellow, but when a test is Inconclusive it's green, shouldn't be the opposite?