You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Fabulich (JIRA)" <ji...@codehaus.org> on 2007/11/21 04:10:57 UTC
[jira] Created: (SUREFIRE-384) Allow TestNG to generate its native
XML output
Allow TestNG to generate its native XML output
----------------------------------------------
Key: SUREFIRE-384
URL: http://jira.codehaus.org/browse/SUREFIRE-384
Project: Maven Surefire
Issue Type: Improvement
Components: TestNG support, xml generation
Reporter: Dan Fabulich
TestNG's native XML output is way richer than JUnit's output. It specifies details about which suites were invoked, which classes contain which methods, which parameters were used in parameterized tests, etc. It can also include the messages printed to stdout, as well as logging information generated with Reporter.log. It's also the basis for TestNG's "rerun failed tests" feature.
Several other bugs and enhancements can't really be done until we do this.
--
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
[jira] Updated: (SUREFIRE-384) Allow TestNG to generate its native
XML output
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich updated SUREFIRE-384:
----------------------------------
Fix Version/s: 2.4
> Allow TestNG to generate its native XML output
> ----------------------------------------------
>
> Key: SUREFIRE-384
> URL: http://jira.codehaus.org/browse/SUREFIRE-384
> Project: Maven Surefire
> Issue Type: Improvement
> Components: TestNG support, xml generation
> Reporter: Dan Fabulich
> Fix For: 2.4
>
>
> TestNG's native XML output is way richer than JUnit's output. It specifies details about which suites were invoked, which classes contain which methods, which parameters were used in parameterized tests, etc. It can also include the messages printed to stdout, as well as logging information generated with Reporter.log. It's also the basis for TestNG's "rerun failed tests" feature.
> Several other bugs and enhancements can't really be done until we do this.
--
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
[jira] Closed: (SUREFIRE-384) Allow TestNG to generate its native
XML output
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich closed SUREFIRE-384.
---------------------------------
Resolution: Fixed
fixed in revision 597190
> Allow TestNG to generate its native XML output
> ----------------------------------------------
>
> Key: SUREFIRE-384
> URL: http://jira.codehaus.org/browse/SUREFIRE-384
> Project: Maven Surefire
> Issue Type: Improvement
> Components: TestNG support, xml generation
> Reporter: Dan Fabulich
> Fix For: 2.4
>
>
> TestNG's native XML output is way richer than JUnit's output. It specifies details about which suites were invoked, which classes contain which methods, which parameters were used in parameterized tests, etc. It can also include the messages printed to stdout, as well as logging information generated with Reporter.log. It's also the basis for TestNG's "rerun failed tests" feature.
> Several other bugs and enhancements can't really be done until we do this.
--
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