Hi all, I just merged the migration from JUnit3 to JUnit5 to master. For you this means: * You can use all the goodness of JUnit5 features, but do not enable parallel execution without carefull testing * Any new JUnit3 test you write will NOT be executed by the CI What makes a JUnit5 test? * Every test method needs to be annotated with  org.junit.jupiter.api.Test * Every setup and teardown need to be annotated too * TestCase is no longer a base class for test classes * You need to statically import assertions from org.junit.jupiter.api.Assertions Checkout the help page for more details on JUnit5: https://junit.org/junit5/docs/current/user-guide/#writing-tests -- Cedric