[
https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed SUREFIRE-803.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.12
Added code to store/check a token in the plugin context to determine whether
the failsafe summary already on disk is from a previous execution in the
current build vs. output from a previous build.
Then, modified to accumulate test results in the failsafe summary instead of
overwriting (overwrite still happens if the existing output is not from the
current build). This allows multiple failsafe executions in a build without
coping with different output locations for the summaries.
See revIds 1232091 and 1233522.
> Multiple Surefire executions - FAILURE in an execution prevents successive
> from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Assignee: John Casey
> Fix For: 2.12
>
> Attachments: surefire-803-failure-prevents-subsequent-executions.zip
>
>
> Let's have multiple Surefire executions in a single module (different config
> needed).
> A failure of a test in one of these executions prevents running the
> successive.
> Surefire's testFailureIgnore is not an option because it makes a run with
> failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests
> should run.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
