Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 2.7
-
Fix Version/s: 2.7.1
-
Component/s: Maven Failsafe Plugin
-
Labels:None
-
Environment:HideApache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr7-20100219_54049 (JIT enabled, AOT enabled)
OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch: "x86" Family: "windows"ShowApache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr7-20100219_54049 (JIT enabled, AOT enabled) OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch: "x86" Family: "windows"
-
Complexity:Intermediate
-
Number of attachments :
Description
Upgrading maven-failsafe-plugin from version 2.6 to 2.7 causes builds with integration test errors to be reported as successful.
From my understanding, the failsafe verify goal uses the summary file (default: target\failsafe-reports\failsafe-summary.xml) to check whether executed integration tests passed or had any errors. I've pasted the content of this file below as it is generated by the failsafe plugin version 2.6 and 2.7 respectively for the same build with the same integration test errors. It appears that the integration-test goal does not generate this file correctly in version 2.7.
<?xml version="1.0" encoding="UTF-8"?> <failsafe-summary result="255" />
<?xml version="1.0" encoding="UTF-8"?> <failsafe-summary />
The result for this build is that the failsafe plugin version 2.6 fails the build (as it should) while failsafe plugin version 2.7 does not and the build is reported as successful.
Issue Links
- is related to
-
SUREFIRE-674
Build does not fail when tests have errors
-
Activity
Tested the same build containing failing tests with maven-failsafe-plugin-2.7.1-20101222.020133-14. The summary file now once again contains the same stuff as 2.6 produced and the build is failed. Great, thanks! 
This bug almost certainly has the same root cause as
SUREFIRE-674, which has been fixed in r1051569. An updated 2.7.1-SNAPSHOT has been published. If you could re-test this issue with this version we can close this issue and get 2.7.1 released.