[SUREFIRE-596] Junit test output is broken with junit4-7+

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5
• Fix Version/s: 2.5
• Component/s: Junit 4.x support
• Environment: junit 4.7
• Flags: Patch
• Assignee: stephenconnolly
• Reporter: Kristian Rosenvold
• Created: 11/Jan/10 17:13
• Updated: 05/Apr/15 14:53
• Resolved: 12/Jan/10 01:40

Description

There is a bug in the log output for the junit4.7+ provider, where it just says "Result null" instead of outputting the
proper surefire output. Additionally, the concurrent junit provider should really only be used
when the user has requested some concurrent execution model in the configuration.

Workaround at the moment is one of the following:
A) Use surefire-2.4.3 until this is fixed
B) Downgrade to junit 4.6 until this is fixed
C) ignore the problem. This may be possible, but some CI systems also parse the output so it may break the build.

The enclosed patch fixes both problems on svn trunk of surefire, and also includes updated integration tests.