Inconclusive message Not in report output

Bug #1000213 reported by Tyrel Alastair Hunter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit Framework
Fix Released
Medium
Charlie Poole
NUnitLite
Fix Released
Medium
Charlie Poole

Bug Description

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

Related branches

Revision history for this message
Charlie Poole (charlie.poole) wrote :

In general, Inconclusive results are not expected to show up anywhere.

On the other hand, it seems like any result with a message should be displayed somewhere, even an Assert.Success!

We'll have to figure out how to show this.

Changed in nunitlite:
status: New → Triaged
importance: Undecided → Medium
Changed in nunit-3.0:
status: New → Triaged
importance: Undecided → Medium
Changed in nunitlite:
assignee: nobody → Charlie Poole (charlie.poole)
milestone: none → 0.8
Revision history for this message
Charlie Poole (charlie.poole) wrote :

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
Changed in nunitlite:
status: Fix Committed → Fix Released
Changed in nunit-3.0:
milestone: none → 2.9.6
Changed in nunit-3.0:
assignee: nobody → Charlie Poole (charlie.poole)
status: Triaged → Fix Committed
Changed in nunit-3.0:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.