nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Adding a new tab or modifying one of the existing tabs to show
inconclusive results involves changes that we don't want to undertake in
NUnit 2.5. This bug is being re-targeted for the nunit 3.0 project,
which will include significant gui changes.

Inconclusive results are especially problematic because they are
intended to 'disappear' entirely when used in a Theory, but should
probably have much more significance when used in a Test.

There are two workarounds in the current release:

1. Use Assert.Ignore, which gives the test the prominence you desired.
In a SetUp method, it is much more usual to use Assert.Ignore anyway,
since the test is not being run.

2. Use the Properties dialog, accessed from the context menu of the test, to view the message. Of course, you have to first
locate the inconclusive test in the tree to do this.

Charlie

** Project changed: nunitv2 => nunit-3.0

** Changed in: nunit-3.0
   Importance: Low => High

** Changed in: nunit-3.0
       Status: Confirmed => Triaged

-- 
Assert.Inconclusive in SetUp method fails silently
https://bugs.launchpad.net/bugs/591263
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: Triaged

Bug description:
I have a simple test with an instance SetUp method. My SetUp method calls Assert.Inconclusive("message").
When I run through the GUI, the test gets marked with an "?" purple icon, but absolutely no detail text (and in particular, my own "message") appears in any of the tabs.

NUnit 2.5.5.10112