Details
Minor Description
It can be useful to override the fork and ignore behavior of our Surefire unit testing machinery.
For example, this will put only one test into each generated surefire jar and always fork a child JVM to run it:
mvn test ... -Dsurefire.firstPartForkMode=always -Dsurefire.secondPartForkMode=always
Useful for isolating test failures and finding zombies.
Sometimes it is also useful to ignore test failures:
mvn test ... -Dsurefire.testFailureIgnore=true
This will let test suite execution continue even if a test times out. Maven has CLI options for this sort of thing but they don't always work as expected.