Change to NUnit-console
"Charlie Poole" <[email protected]>
| Newsgroups | gmane.comp.windows.dotnet.nunit.devel |
|---|---|
| Message-ID | <000f01c8818a$2da18850$6401a8c0@ferrari> |
Hi All, The new roadmap for NUnit 2.5 (http://nunit.org/?p=roadmap lists one item that I'd like to run by this group... "Eliminate use of stylesheet to format console output and drop the /transform option." The console runner currently creates an xml file and then reformats that file to produce the familiar console output, like this <quote> Tests run: 6, Failures: 0, Not run: 5, Time: 0.063 seconds Tests not run: 1) NUnit.Tests.Assemblies.MockTestFixture.MockTest4 : ignoring this test method for now 2) NUnit.Tests.Assemblies.MockTestFixture.MockTest5 : Method MockTest5's signatu re is not correct: it must be a public method. 3) NUnit.Tests.IgnoredFixture.Test1 : 4) NUnit.Tests.IgnoredFixture.Test2 : 5) NUnit.Tests.IgnoredFixture.Test3 : </quote> The /transform option may be used to change the appearance of that text output, but most people want to use it for an entirely different purpose - to produce an html report file - and are disappointed that it cannot do that. It's really much simpler to maintain the console output in NUnit if it is produced directly, independent of the xml file. My suspicion is that few people - if any - are using the /transform option. It's function can readily be replaced by transforming the xml file as a separate step, which is what you have to do anyway to produce an xml report. This change will make the console runner easier to maintain and doesn't seem to have serious negative impacts - but I'd like to hear from you if there is something I missed. Charlie ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/