nunit-core team mailing list archive

Thread
Date

[Bug 454814] Re: Details Of Inconclusive Tests Missing From XML

To: nunit-core@xxxxxxxxxxxxxxxxxxx
From: Charlie Poole <charlie@xxxxxxxxx>
Date: Tue, 13 Apr 2010 04:33:21 -0000
Reply-to: Bug 454814 <454814@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nunitv2
       Status: Fix Committed => Fix Released

-- 
Details Of Inconclusive Tests Missing From XML
https://bugs.launchpad.net/bugs/454814
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.

Status in NUnit V2 Test Framework: Fix Released

Bug description:
Details of inconclusive tests are missing from the GUI/console XML output. Whilst the number of inconclusive tests is correctly reported on the test-results element there doesn't seem to be anything obvious to determine which tests were inconclusive. The relevant test-case elements have executed="True" and success="False".

The inconclusive tests do lack a child failure element in the test-case element but if this is the only difference between failure and inconclusive then I'd like to see something more concrete, i.e. something that states definitely this test is inconclusive rather than stating that a test hasn't succeeded and hasn't failed.

Also a message can be specified with calls Assert.Inconclusive; this does not appear in the XML either.

Perhaps include a child <inconclusive> element to specify a test is inconclusive and also include any message inside that?