[jira] Updated: (SUREFIRE-561) after running test, when tests fail, it's hard to the find the failure reason

["Kristian Rosenvold (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/SUREFIRE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Rosenvold updated SUREFIRE-561:
----------------------------------------

    Component/s: Maven Surefire Plugin

> after running test, when tests fail, it's hard to the find the failure reason
> -----------------------------------------------------------------------------
>
>                 Key: SUREFIRE-561
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-561
>             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 summary.
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira