nunit-core team mailing list archive

Thread
Date

[Bug 1000213] Re: Inconclusive message Not in report output

To: nunit-core@xxxxxxxxxxxxxxxxxxx
From: Charlie Poole <charlie@xxxxxxxxx>
Date: Sat, 21 Jul 2012 20:14:35 -0000
Reply-to: Bug 1000213 <1000213@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

For NUnitLite, I added a <reason> element with the message for
inconclusive and success results provided the message is not null. We
may want to change this.

** Changed in: nunitlite
       Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/1000213

Title:
  Inconclusive message Not in report output

Status in NUnit Test Framework:
  Triaged
Status in NUnitLite Testing Framework:
  Fix Committed

Bug description:
  When using Assert.Inconclusive("The test was inconcluive because ..........")
  The message does not show in the report.xml file

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-3.0/+bug/1000213/+subscriptions