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/23 08:11:57 UTC
[jira] Closed: (SUREFIRE-353) Link to test JavaDoc in test repor
[ http://jira.codehaus.org/browse/SUREFIRE-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich closed SUREFIRE-353.
---------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 2.x)
We're limited to the information available in the JUnit XML output for information like this. Fortunately, the surefire-report plugin knows how to integrate with JXR for test failures, so you can click through to see the source code of offending test failures; that should be enough information to analyze the test results.
> Link to test JavaDoc in test repor
> ----------------------------------
>
> Key: SUREFIRE-353
> URL: http://jira.codehaus.org/browse/SUREFIRE-353
> Project: Maven Surefire
> Issue Type: New Feature
> Components: report plugin
> Reporter: Francois Loison
> Priority: Minor
>
> Current report could be improved by displaying functional information of test cases.
> For exemple:
> TestX : tests functionality X
> One way should be to document test case functionality in javadoc and add an hyperlink in surefire report to javadoc.
> If feature agreed, I could propose some code.
> francois.loison@wanadoo.fr
--
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