You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Evan Worley (JIRA)" <ji...@codehaus.org> on 2007/06/05 05:45:59 UTC
[jira] Issue Comment Edited: (NMAVEN-73) NUnit output is
inconsistent with maven-test-plugin output
[ http://jira.codehaus.org/browse/NMAVEN-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98371 ]
Evan Worley edited comment on NMAVEN-73 at 6/4/07 10:44 PM:
------------------------------------------------------------
It was mentioned on the mailing list that one option is to implement a surefire provider for nunit
was:
One implementation suggestion that Brett suggested was possibly creating a surefire provider for nunit
> NUnit output is inconsistent with maven-test-plugin output
> ----------------------------------------------------------
>
> Key: NMAVEN-73
> URL: http://jira.codehaus.org/browse/NMAVEN-73
> Project: NMaven
> Issue Type: Improvement
> Environment: Maven 2.0.4 with NMaven 0.14-SNAPSHOT
> Reporter: Evan Worley
> Priority: Minor
>
> I was thinking there would be some value in doing some work on the nunit plugin to add some output similar to the junit plugin. Currently when nunit tests run, all the output is logged to file. It is not too much fun when your tests run for a few minutes, you see nothing. Here is a junit output vs nunit output comparison
> -- JUNIT --
> Running package1.TestClass1
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
> Running package2.TestClass2
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
> .
> .
> .
> Results :
> Tests run: 139, Failures: 0, Errors: 0, Skipped: 0
> -- NUNIT --
> NMAVEN-040-000: Executed command: Commandline = nunit-console C:\dev\project \main\component\target\test-assemblies\Namespace.Artifact.dll /out {SOME_OUTPUT_FILE} /err {SOME_OUTPUT_FILE}, Result = 0
> The nmaven test plugin should capture the stdout/stderr from nunit and format is similar to junit. These inconsistencies are especially noticed in environments where you build the same component in java and C#. Switching from the java to C# build seems like a whole new world, instead of simply a new language
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira