[ 
https://issues.apache.org/jira/browse/SUREFIRE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959660#comment-14959660
 ] 

Tibor Digana commented on SUREFIRE-1183:
----------------------------------------

Actually we agreed on pre-release of 3.0 where we want to get an impression 
from Maven users, it means you as well. The pre-release would be 2.20/2015 with 
Java extensions API and SPI. Later we can think of scripting languages but 
that's not mandatory at the moment. So I see the opportunity in surefire-report 
plugin because this SPI would be best applied in in-process unlike in the 
forked process of surefire/failsafe-plugin. Maybe later we would be able to 
customize not only report names but also the structure in the page.

> Custom Test Report Titles and Descriptions
> ------------------------------------------
>
>                 Key: SUREFIRE-1183
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1183
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Surefire Report Plugin
>    Affects Versions: 2.18.1
>            Reporter: Gerald Mücke
>            Priority: Minor
>
> Hi,
> I'd like to add the possibility to customize the name and descriptions of the 
> test reports, in order to define report sets with not only custom outputNames 
> but custom titles and descriptions as well so that they appear in the report 
> with a self-describing name and description.
> Motivation:
> At a customer project we have several automated tests (unit tests, 
> integration tests, automated acceptance tests, performance tests) and each of 
> those are run either using surefire or failsafe. 
> We have different report sets for each of these tests and separate output 
> files. But in the Project Reports Overview each Report is named either 
> "Surefire Report" or "Failsafe Report" with the corresponding default 
> description. Further, the title of the Report page itself is always "Surefire 
> Reports"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to