NUnit output format does not match


The NUnit format emitted by statlight does not conform closely enough to allow support by some tools, notably by NUnitResults ( https://launchpad.net/nunit-results ).

There seem to be two critical differences. The main one is that the time format does not match the standard NUnit format. Here is statlight:

Here is NUnit:

The confluence of these issues causes other tools to crash.

The time format issue may also be an issue in the MSTest format.

file attachments


archastrel wrote Nov 2, 2012 at 6:53 PM

Added that description in a text file, since the codeplex interface did not seem to like the use of angle brackets in the description.

wrote Nov 2, 2012 at 6:55 PM

staxmanade wrote Nov 4, 2012 at 3:51 AM

Thanks for reporting this issue.

Is launchpad.net a location that is failing? Do you know how I could reproduce this on my side (without too much setup?) :) Or do you know of any other tools that would be easy to test the output with and verify?

I do have the XML schema definition in the project and when I originally wrote the NUnit provider it did pass the XSD. (https://github.com/staxmanade/StatLight/blob/master/src/StatLight.Core/Resources/NUnitXmlResults.xsd)

Due to versioning issues with the .net framework I ended up dropping this schema validation from my continuous build. So at the moment I'm not sure if it still passes the XSD.


wrote Feb 14, 2013 at 8:17 PM