1

Closed

Add Support For Inconclusive Tests

description

Both NUnit and MSTest have a concept of inconclusive tests; make sure they are transformed correctly.
Closed Nov 28, 2009 at 11:23 AM by

comments

MrKWatkins wrote Oct 18, 2009 at 5:12 PM

Turns out there isn't anything like inconclusive="True" in the NUnit output to make this nice and easy. Inconclusive tests have success="False" on their test-case element just like failures; however they lack a child failure element. Details of inconclusive messages (from Assert.Inconclusive(string)) are not included in the XML. I have raised a bug with NUnit (https://bugs.launchpad.net/nunitv2/+bug/454814) as I feel there should be something to indicate definitely that a test is inconclusive. Will wait for the results of that before adding anything to the XSLT.

MrKWatkins wrote Nov 28, 2009 at 10:40 AM

Looking at the source code for NUnit we can determine whether a test was inconclusive or not. If the test has failed the element will have a child element for ResultStates of Failure, Error or Cancelled. For ResultStates of NotRunnable, Skipped or Ignored it will have a child element. Therefore if it has neither it can only have a ResultState of Inconclusive.

wrote Nov 28, 2009 at 10:40 AM

Resolved with changeset 31541.

MrKWatkins wrote Nov 28, 2009 at 11:02 AM

** Closed by MrKWatkins 11/28/2009 3:40 AM

MrKWatkins wrote Nov 28, 2009 at 11:02 AM

wrote Nov 28, 2009 at 11:23 AM

Resolved with changeset 31545.

Sign in to add a comment