[
https://jira.codehaus.org/browse/SUREFIRE-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358640#comment-358640
]
Roy Arnon edited comment on SUREFIRE-1122 at 12/4/14 4:58 PM:
--------------------------------------------------------------
I has some time to burn, so I modified the test project - simply run mvn test,
and you should see 4 test cases - 2 fail with the parallel option, and 2
succeed without it.
One tests that the output xml file contains a flakyFailure tag, the other that
the file contains 2 testscases.
They are pretty simple, got too lazy to use an xml parser so just used contains
string :).
Otherwise, they run the same code - clean verify on the test project.
was (Author: hellspam):
I has some time to burn, so I modified the test project - simply run mvn test,
and you should see 4 test cases - 2 fail with the parallel option, and 2
succeed without it. Otherwise, they run the same code - clean verify on the
test project.
> When running failsafe with -Dfailsafe.rerunFailingTestsCount and parallel
> all, the reports are not generated correctly
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1122
> URL: https://jira.codehaus.org/browse/SUREFIRE-1122
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 2.18
> Reporter: Roy Arnon
> Attachments: invalid.xml, test.zip, valid.xml
>
>
> Hi,
> I just tried the new feature -Dfailsafe.rerunFailingTestsCount on our
> failsafe build.
> Unfortunately, when running the build using parallel=all, it seems the junit
> xml files are not generated correctly.
> I've tried running it multiple different ways, including classedAndMethods,
> and all, but it seems to generate an incorrect xml file either way.
> I've attached both files here.
> I can provide a pom and java test case if required.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
