maven-surefire-plugin and maven-failsafe-plugin have been updated to 3.0.0-M5. This fixed a bug, that tests which failed within the setup phase of a test instance were not marked as failed.

Thus, after upgrade, you may experience tests, which fail afterwards. This typically signals tests, which were silently ignored before this update. We stumbled across such an issue within Spring based tests, where required beans were missing in the test context.

While doing the Maven plugin updates, we also updated testing libraries especially because JUnit and Surefire/Failsafe have a strong interaction. The following libraries have been updated to the given versions:

One additional learning from the migration: Depending on your build process you may experience classes not being found when executing maven-failsafe-plugin . This is due to a change in the behavior of the default of the <classesDirectory> configuration which clashes with some repackage-JAR mechanisms. If you experience class loading issues after upgrade, you may want to consider a workaround we used, which is explicitly setting <classesDirectory> :

<configuration>
  <classesDirectory>${project.build.outputDirectory}</classesDirectory>
</configuration>

(CMS-17989)