I am using Maven surefire plugin 2.4.2 with the following configurations:
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
...
<testFailureIgnore>false</testFailureIgnore>
...
<forkMode>always</forkMode>
...
</configuration>
</plugin>
I have intentionally set testFailureIgnore=false (i.e. the default value),
so that if the test fails the build process fails. However when my tests
fail with ERROR, i see that irrespective of this property value, the rest of
the build is carried out and the build reports a SUCCESS.
A bit of debugging and playing with the forkMode, shows that the
testFailureIgnore=false results in the build to fail (which is what i
expect) *only* when the forkMode is set to "never". Setting the forkMode to
always or once always results in a successful build irrespective of the
testFailureIgnore setting.
Is this the expected behaviour?
--
View this message in context:
http://www.nabble.com/Maven-surefire-plugin---testFailureIgnore-and-its-behaviour-with-forkMode-tp22782458p22782458.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
