JUnit 5 Release Notes

Full stacktrace is printed to the console, when running the ConsoleLauncher in --details verbose mode.

ReflectionUtils.findNestedClasses() and ReflectionSupport.findNestedClasses() no longer allow a NoClassDefFoundError to propagate if a nested class or nested interface has an invalid class file. Instead, the error will now be swallowed and logged at WARNING level.

The junit-platform-gradle-plugin has been discontinued and is no longer released as part of JUnit 5. Please use Gradle’s native support for running tests on the JUnit Platform (requires Gradle 4.6 or higher) instead.

The findAnnotation() methods in AnnotationSupport and AnnotationUtils no longer cache annotation lookups. Note, however, that the algorithm remains otherwise unmodified and is therefore semantically identical to the previous behavior.

Experimental support for capturing output printed to System.out and System.err during test execution. This feature is disabled by default and can be enabled using a configuration parameter (cf. User Guide).

Reusable support for parallel test execution for test engines that extend HierarchicalTestEngine.

New overloaded variant of isAnnotated() in AnnotationSupport that accepts Optional<? extends AnnotatedElement> instead of AnnotatedElement.

New --fail-if-no-tests command-line option for the ConsoleLauncher.

When using @TestInstance(Lifecycle.PER_CLASS) semantics, registered AfterAllCallback extensions are no longer invoked if an exception is thrown by the test class constructor. Consequently, AfterAllCallback extensions are now only invoked if BeforeAllCallback extensions were invoked.

Test discovery no longer halts prematurely if a nested class or nested interface in a test class has an invalid class file.

Certain categories of errors encountered during the test discovery phase no longer cause JUnit Jupiter to prematurely abort the entire discovery process.

Experimental support for parallel test execution. By default, tests are still executed sequentially; parallelism can be enabled using a configuration parameter (please refer to the User Guide for examples and configuration options).

New support for the IBM AIX operating system in @EnabledOnOs and @DisabledOnOs.

New assertThrows methods in Assertions provide a more specific failure message if the supplied lambda expression or method reference returns a result instead of throwing an exception.

New arguments() static factory method in the Arguments interface that serves as an alias for Arguments.of(). arguments() is intended to be used via import static.

New get<Class>(index) Kotlin extension method to make ArgumentsAccessor friendlier to use from Kotlin.

New support for supplying a custom test source URI when creating a dynamic container or test. See factory methods dynamicContainer(String, URI, …​) in DynamicContainer and dynamicTest(String, URI, Executable) in DynamicTest for details.

Tag expressions containing spaces are now supported in the JUnit Platform Maven Surefire provider.

Duplicate --config keys supplied to the ConsoleLauncher are now reported properly.

Exceptions thrown in Node.after() (in the HierarchicalTestEngine infrastructure) no longer mask earlier exceptions.

The JUnit Platform Surefire Provider (junit-platform-surefire-provider) now works with and requires Surefire 2.21.0 which allows it to be used with Java 9 and Java 10.

The default include pattern for filtering class names now matches test classes whose names either start with Test or end with Test or Tests.

Exceptions thrown by an AfterAllCallback no longer mask exceptions thrown at the class level when using the @TestInstance(PER_CLASS) lifecycle mode.

New assertDoesNotThrow() methods in Assertions which assert that the execution of a given code block does not throw any kind of exception.

New fail() method in Assertions makes it possible to fail a test without an explicit failure message.

Implicit support for widening primitive conversion for an argument supplied to a @ParameterizedTest.

@MethodSource now supports static factory methods declared in external classes referenced by fully qualified method name.

Support for aggregation of multiple @ParameterizedTest arguments into a single object.

New findAllClassesInModule() method in ReflectionSupport which enables third-party TestEngine implementations to scan for classes in modules — for example, when processing a ModuleSelector during the discovery phase.

The ParameterContext API used in ParameterResolver implementations now includes the following convenience methods for looking up annotations on parameters. Extension authors are strongly encouraged to use these methods instead of those provided in the core java.lang.reflect.Parameter API due to a bug in javac on JDK versions prior to JDK 9 which causes lookups for annotations on parameters in inner class constructors to fail consistently — for example, when resolving a parameter for a @Nested test class constructor.