[SUREFIRE-672] Failsafe no longer fails builds due to broken failsafe-summary.xml file

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.7
• Fix Version/s: 2.7.1
• Component/s: Maven Failsafe Plugin

Environment

Apache 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"

• Assignee: Kristian Rosenvold
• Reporter: Jan Fredrik Wedén
• Created: 21/Dec/10 06:05
• Updated: 22/Dec/10 02:55
• Resolved: 22/Dec/10 02:55

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.

failsafe plugin v2.6: failsafe-summary.xml

<?xml version="1.0" encoding="UTF-8"?>
<failsafe-summary result="255" />

failsafe plugin v2.7: failsafe-summary.xml

<?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