| Mike Duigou Falko Modler We cannot modify the purpose of maven.test.failure.ignore . Let's explain it: The test set will end up with Result Set (total, failures, errors, flakes, skipped) and the test frameworks (JUnit, TestNG, etc) provide RunListener sending the test events into the final Result Set. All the teminology you can see in maven.test.failure.ignore{{ }}talks abou failures and it means the Result Set. It has nothing to do with any timeouts and vice versa! If we have to fix this without touching the TXT and XML reports, I am all the ear how. My proposal is to introduce surefire.failIfTimeout=true and failsafe.failIfTimeout=true. It is complemetary principle to the parameter that we already have with failIfNoTests=true. So we control the behavior on fine grained level. Setting maven.test.failure.ignore=true would not bypass the failIfNoTests=true and the build fails anyway with not having any tests in the project. The same should be with the timeouts. The only difference are the default values, where failIfNotests has false, and failIfTimeout would have true. If the user wants to completely avoid build failure, run the cmd mvn test -Dmaven.test.failure.ignore=true -Dsurefire.failIfTimeout=false If the user wants to avoid test failure(s) run the cmd mvn test -Dmaven.test.failure.ignore=true Feel free to comment on this. |
