[
http://jira.codehaus.org/browse/SUREFIRE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated SUREFIRE-253:
----------------------------------
Component/s: report plugin
> Add integration logic that allows report to be created for junit OR testng
> --------------------------------------------------------------------------
>
> Key: SUREFIRE-253
> URL: http://jira.codehaus.org/browse/SUREFIRE-253
> Project: Maven Surefire
> Issue Type: Improvement
> Components: report plugin
> Environment: any
> Reporter: Jesse Kuhnert
> Assigned To: Allan Ramirez
> Fix For: 2.0 Report Plugin
>
> Attachments: maven-surefire-report-maven-plugin-patch.txt,
> testngjunit.diff
>
> Original Estimate: 3 hours
> Time Spent: 3 hours
> Remaining Estimate: 0 minutes
>
> I'm currently in the middle of patching/working with testng and the
> maven-surefire plugin core parts to provide a seamless testng integration
> point and am on the final task of getting the report to be a little
> friendlier. This is the jira issue for the surefire portion:
> http://jira.codehaus.org/browse/MSUREFIRE-23
> I think at the very least I wanted to change the runtime to ~not~ try and
> parse class/package constructs out of the test name attributes, but work in
> an agnostic manner to just group things as they appear in the xml output. I
> also intend to embed a very minimal amount of javascript into the generated
> html page so that report errors/stack traces can have hide/show buttons
> enabling the detailed viewing of their contents.
> Does this sound reasonable to everyone? I've got the source checked out right
> now and will be working on this today.
--
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
