Release Notes

❓

❓

When using ConsoleLauncher with the -cp/--classpath option, it now creates a custom ClassLoader that does not implement AutoCloseable to avoid accidentally closing it in test code which can lead to test failures that are hard to diagnose.

When using a third-party engine that uses the junit- prefix a discovery issue is emitted.

junit-platform-console-standalone is now part of the junit-bom

@org.junit.platform.suite.api.Disabled can be used annotate a @Suite-annotated class. If so annotated, the suite will not be executed.

The org.junit.jupiter.api.assertThrows Kotlin API and its related functions have added variants that use an exception class as a value rather than a type parameter. This is to primarily to address the current issue/s when trying to use @ParameterizedTest that produces exceptions as values.

The junit.jupiter.params.displayname.argument.maxlength configuration parameter is now validated and rejected with a clear error when set to a non-positive value instead of causing parameterized tests to fail with an internal exception.

The elements of @CsvSource.value[] are now treated as individual CSV documents. This prevents unfinished quotes in one document from affecting another.

❓

Added OS.NETBSD and OS.DRAGONFLYBSD enum constants for use with @EnabledOnOs and @DisabledOnOs.

Failures caused by @Timeout expirations now include a hint about enabling thread dumps.

❓

❓

❓

❓

❓

❓

❓

❓

❓

❓

❓

❓

Fix NoTestsDiscoveredException for suites containing only dynamic tests

The Suite Engine no longer logs "No TestIdentifier with unique ID" for failing tests.

Allow excluding engines from memory cleanup mode (in case it’s enabled) via new junit.platform.execution.memory.cleanup.engines.excluded configuration parameter that takes a comma-separated list of engine IDs (for example, junit-vintage,junit-jupiter).

Restore original values set by @SetSystemProperty when used with a @ParameterizedTest.

JAVA_28 has been added to the JRE enum for use with JRE-based execution conditions.