Re: NUnit XML Output

As for definitions, my definition for "log" is simply test results, just
like Mark's. That's the reason why we suggest modifying TestResults.xml as a
possible solution. I myself see no need for two "log" files. Maybe this
could be a configurable option? For example, my test are neither parallel
nor not completing for a long time... So I choose to use writing
TestResults.xml after each test/fixture. If that causes me problems, I
choose to do it the old way.

As for what exactly is expected to be accomplished, as I see it, it's simply
having test results in a file as current as possible (i.e., after each test
or at least test fixture).

> However, as I asked in an earlier note, why not just use
> NUnit's console output, which can be set to list each test
> as it executes? That would certainly tell you which test
> caused a hang.

I would think of three things here:
1. If NUnit crashes, which is my reason for logging, I would not see the
console output anyway (or is it stored in some file?).
2. I would have to write to console at each test, which is not so much
different from writing to my own XML file instead.
3. Mark's reason for incremental logging is grabbing the results in
CruiseControl, which is not possible with simply writing to console (except
if the console output is stored in a file, again).

Regards,
Aiste




 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3368 (20080819) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 


-------------------------------------------------------------------------
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=/