You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2011/12/11 18:16:02 UTC
[jira] (SUREFIRE-803) Multiple Surefire executions - FAILURE in an
execution prevents successive from running.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285535#comment-285535 ]
Kristian Rosenvold commented on SUREFIRE-803:
---------------------------------------------
I think this could probably go "as is" wrt the current failsafe plugin. I somehow think we can just change the default behaviour on this one; if a user currently has multiple executions of failsafe she'll be losing the results from one of the invocations; i just don't see the use case where the existing behaviour makes sense (unless you also attach ver ify multiple places, but that wouldn't change even if we did this change).
Regarding how to detect which executions have been done, I've been wondering if we could just keep a list of executions in the pluginContext ? I'm not sure why we need to write the results to a file (and an xml file, just to be sure..). Maybe stephen has some input on this..
> 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: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Assignee: John Casey
> Priority: Critical
> 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