Re: NUnit XML Output

Ron Grabowski <[email protected]> Tue, 19 Aug 2008 14:37:01 -0700 (PDT)
Newsgroups gmane.comp.windows.dotnet.nunit.user
Message-ID <[email protected]>
TestResults.xml seems to imply the output of the user tests that are running. If your issue is with how NUnit is running the tests can't you capture its internal events as Charlie suggested? From glancing at the source there appears to be several extension points. If you think something is failing at a very low level before you can setup the listener in code perhaps NUnit could be configured to look for a special event listener Type in App.Config and raise events to that. That might give you access to things like issues with initialize any static objects NUnit might be using. log4net writes output through the System.Diagnostics libraries and/or Console.Writeline when its internal debug mode is activate.



----- Original Message ----
From: Laimonas Simutis <[email protected]>
To: [email protected]
Sent: Tuesday, August 19, 2008 4:49:58 PM
Subject: Re: [Nunit-users] NUnit XML Output

On Tue, Aug 19, 2008 at 3:24 PM, Aiste Stikliute <[email protected]> wrote:
> 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.

I will have to disagree here. The log is the log and the test results
are the test results. IMO they are two separate things.
TestResults.xml is pretty much a summary of the test run.

I would focus on a previous conversation which indicated that for this
"real-time" logging we need some sort of different mechanism of output
where interested parties could look at. You wouldn't need to look at
it all the time, (I mean a mysterious test failing out of the sudden
is not a usual behavior I would hope)

Just my opinion ...

-------------------------------------------------------------------------
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=/
_______________________________________________
Nunit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nunit-users


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