Re: NUnit XML Output

2008/8/14 Charlie Poole <[email protected]>:
> We don't write the xml file incrementally although a feature
> request was submitted just a few days ago asking for this.
>
> While it is a "dev" issue, I'm about to merge the lists
> anyway, so lets disuss it.
>
> Pros (as I see them):
> * If the test run hangs or crashes, we can see how far
>  it got.
> * Software (CI for example) can "watch" the progress
>  of the tests
>
> Cons:
> * It needs to be carefully thought out so we don't end
>  up with XML-creation code all over the place.
> * Using the most naïve implementation, the XML file would
>  be invalid until we terminated it - which means we
>  would need a smarter approach.
>
> One possibility is to NOT do this with the XML file but
> to simply write a log of some kind. I'm not sure that
> this would satisfy everyone though.
>
> What do others think?
>
> Charie

I'm more familiar with junit XML format than nunit's. Junit has syntax like:
<testfixture name="blah" assertions="5" failures="2" errors="11">

That cannot be done incrementally. I take it nunit's xml is more
friendly to incremental output, if you're even mentioning the
possibility. But it would still be ugly. I think I prefer logging via
some non-XML format, on the whole.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/