[jira] Updated: (MSUREFIREREP-22) Aggragated surefire report from modules

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] Updated: (MSUREFIREREP-22) Aggragated surefire report from modules

JIRA jira@codehaus.org
     [ http://jira.codehaus.org/browse/MSUREFIREREP-22?page=all ]

J-C updated MSUREFIREREP-22:

    Attachment: patch.patch

I patch surefire-reporting 2.0 to include an report for pom packaging.

In 2.0, report is done only if language is java. In my patch it is also apply on pom packaging file.

When packaging is pom, it checked for modules and create a report page that contains the total number of test executed, failed, ...

If there is some failure, test in failure are listed ordered by module. It supports several level of modules. A hyperlink on the module title allow to navigate to the reporting page of the module

I tried it on a sample project:

Sample(packaging pom)
  |-------> sample 1 (jar with some failure in testcase)
  |-------->sample 2 (jar with some failure in testcase)
  |-------->sample 3 (packaging pom)
                   |-------->sample 4 (jar with some failure in testcase)

Aggregated report looks like report.jpg

Problem is that before running the plugin tests must have been executed.

It might be a nice feature to include that patch in surefire-reporting ...

> Aggragated surefire report from modules
> ---------------------------------------
>                 Key: MSUREFIREREP-22
>                 URL: http://jira.codehaus.org/browse/MSUREFIREREP-22
>             Project: Maven 2.x Surefire report Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.0
>         Environment: all
>            Reporter: Bugittaa Pahasti
>         Attachments: patch.patch, report.JPG
> Aggregated surefire report from child modules. I think this has been discussed in the mailing lists, but seemed not to be on Jira yet.

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