[
http://jira.codehaus.org/browse/SUREFIRE-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold closed SUREFIRE-730.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.8.2
Assignee: Kristian Rosenvold
Thanks a lot for this report, it's the root cause of a number of other bugs we
have in the issue trackers.
Fixed with a slightly different patch and a unit test in r1095165.
> JUnit4RunListener does not report results from concurrently running tests
> correctly
> -----------------------------------------------------------------------------------
>
> Key: SUREFIRE-730
> URL: http://jira.codehaus.org/browse/SUREFIRE-730
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Affects Versions: 2.5, 2.8.1
> Reporter: James Neal
> Assignee: Kristian Rosenvold
> Priority: Critical
> Fix For: 2.8.2
>
> Attachments: sure.dif
>
>
> JUnit4Listener determines succesful pass of a test via a single boolean flag
> on the class that is set when a test to "true" when a test is started, set to
> "false" when a test failed, and checked after a test finishes. If all the
> tests run in serial, this scheme works, but when the tests are all run in
> parallel, after the first failed test no other successful tests will be
> reported as having been run (because after the flag is set to "fail" nothing
> ever resets it - all the tests have already started).
> It would be simple to fix this by changing the single failure flag to a hash
> map of tests to pass/fail flags, and such a change would greatly improve my
> quality of life.
--
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
