[Mono-dev] SPAM-LOW: Re: NUnit migration and test failure status

[Charlie Poole]

Hi Atsushi,

I'm confused about what change you could be refering to.
NUnit-console still outputs error summaries to the console
in 2.4.8 (and 2.5 for that matter). But some things have
changed in the 18 releases since 2.2. :-)

I'm guessing, but I suspect you have redirected output
using -out on the command line. In 2.4.8, this *only*
redirects the actual test output, not the summary
report, which still goes to stdout. If you want 
everything in one file, stop using -out and use
shell redirection instead. If you want to separate
the summary from the test output, then you can use
both methods, like...

nunit-console ... -out:TestDetails.log > TestSummary.log

If this doesn't help, send me some more info and 
we'll either figure out how to do it or change
for 2.4.9.

Charlie

> -----Original Message-----
> From: mono-devel-list-bounces at lists.ximian.com 
> [mailto:mono-devel-list-bounces at lists.ximian.com] On Behalf 
> Of Atsushi Eno
> Sent: Monday, December 01, 2008 3:58 AM
> To: mono-devel-list at lists.ximian.com
> Subject: SPAM-LOW: Re: [Mono-dev] NUnit migration and test 
> failure status
> 
> Another limitation brought by this migration is that to see 
> meaningful TestResult-*.log you will have to install xsltproc 
> (in general in
> libxslt) as nunit-console itself does not output test failure 
> summaries to console output anymore and we sort of needed xslt output.
> 
> It is not required unless you run tests. And if you run tests 
> it will be anyways needed to see meaningful logs.
> 
> Atsushi Eno
> 
> Atsushi Eno wrote:
> > Hello,
> > 
> > As some of you may have noticed, I have upgraded our local use of 
> > nunit from 2.2.0 to 2.4.8. It involved some changes in our 
> test run, 
> > but should be invisble to most of you.
> > 
> > The build has been broken for a while (am sorry for that; 
> it was a set 
> > of make dist / packaging mess), and now we have a couple of test 
> > failures. So before Marc dives into the hell list of 
> unknown bugs to 
> > him, I wanted to give some survey on them:
> > 
> > - some JIT stuff: test-verifier, test-System_Web-2.0
> > - mere build failure: test-System_Data-2.0
> > - some floating point failures: test-corlib-*, 
> test-System_Drawing-*,
> >   test-System_Data-1.0, test-System_Runtime_SFS-*
> > - possible NUnit run changes: test-corlib-2.0
> >   (MonoTests.System.Threading.ExecutionContextTest.Copy_FromThread),
> >   test-System_Runtime_Remoting-*
> > - possibly gdiplus: test-System_Drawing-*, test-Windows_Forms-2.0
> >   (MonoTests.System.Drawing.PenTest.DashCap_Valid)
> > - some sys.data changes: test-Mono_Data_Sqlite-*,
> >   test-Mono_Data_SqliteClient*
> > 
> > The only pattern I am concerned is the one with (possible) 
> NUnit run 
> > changes. NUnit 2.4.8 now requires -noshadow to get our 
> tests run fine.
> > This also happens under .NET (i.e. make run-test-ondotnet) even 
> > without -noshadow, so I am rather afraid that NUnit 2.4.8 
> unlike 2.2.0 
> > cannot handle it.
> > 
> > I'd like to hear inputs on what could be done to fix this issue.
> > 
> > Atsushi Eno
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> > 
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>