Re: 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.

Yes. Generally, people want TestResult.xml to reflect the structure
of the tests, not the way they are executed. That way, it's possible
to compare results from week to week, for example. Of course, in the
simplest case, the test execution order is the same as this structure
and we could have used it for two purposes in the past as a matter
of expediency.

Right now, at the point where various ways of running the tests
(parallell, distributed, etc.) are coming into play doesn't seem
to be the time to introduce a restriction on how this is produced.

I see any logs, for example, as being local to the machine on
which the test is run, while the summary report will remain on
the machine that initiated the run. Similarly, I would expect a
log to reflect the order of events as they happened, including
the possibility that the starts and ends of test may be 
interleaved. OTOH, the summary file would follow the order in
which the tests were defined or be sorted in various ways for
convenience.


> 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)

I've been able to resolve dozens of similar scenarios by 
simply looking at the text output from nunit-console. The
/labels option causes the name of every test method to be
output when it starts.

Charlie

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