maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek (JIRA)" <>
Subject [jira] Commented: (SUREFIRE-561) after running test, when tests fail, it's hard to the find the failure reason
Date Thu, 17 Feb 2011 13:44:22 GMT


Alexander Klimetschek commented on SUREFIRE-561:

For working with the file reports, have a look at SUREFIRE-701 - it provides a showSuccess=false
option that simply omits successful reports. Together with disableXmlReport=true to get rid
of the xml files in target/surefire-reports, very useful when you develop & only look
for the failed test reports.

> after running test, when tests fail, it's hard to the find the failure reason
> -----------------------------------------------------------------------------
>                 Key: SUREFIRE-561
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.4.3
>            Reporter: Szczepan Faber
> Maven & surefire has been here for a while but still I'm missing this feature. When
my tests fail, I'd like to know exact failure reason.
> 1. Surefire summary does not show the stack trace / line number / assertion. Browsing
results files in target dir is frustrating & time consuming.
> 2. It is impossible to use surefire-report plugin in fully automated way. If I plug report-only
goal to phase test, this goal is not executed when phase test fails
> Current workaround in my project is that every maven submodule has a handy batch file
with 'mvn surefire-report:report-only'.
> One of the ways of implementing it is adding stacktrace/assertion information in test
> What do you guys think about this idea?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message