Release Notes

When scanning the classpath, the resolved path is used to cache an open jar file system rather than a (potential) symlink.

HierarchicalTestEngine implementations now wait for the dynamic tests a node has already submitted even if the node’s execute() method throws an exception. Previously, with parallel execution, such dynamic tests could finish after their parent, e.g. when the arguments source of a @ParameterizedTest or @ParameterizedClass or the children stream of a DynamicContainer threw an exception.

The generic type parameters of Try methods now consistently allow nullable types.

When scanning the classpath, a separate file system is now created for each jar file rather than a shared one. Thus, classpath scanning no longer fails or interferes with other code if a file system for the same jar file has already been opened elsewhere.

Classpath scanning now finds packages within jar files whose names contain non-ASCII characters.

❓

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.

ConsoleLauncher with --details=verbose now reports on each test atomically and indents its output correctly when tests are executed in parallel. Previously, the reported output from different tests could interleave.

Test Engine and Jupiter Extension authors may generate a machine-readable overview of configuration parameters. See Documenting Configuration Parameters for more information.

Platform configuration parameters are documented in META-INF/junit-platform-configuration-metadata.json

Test engines using the ParallelHierarchicalTestExecutorServiceFactory now use the WORKER_THREAD_POOL executor service by default.

Test engines may now access the store scoped to the enclosing launcher session via the new EngineDiscoveryRequest.getSessionScopedStore() API. This can be used to store or cache information that is reused during test execution or later discovery phases.

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.

@Nested test classes declared in super classes of a test class are now discovered and executed even if they have the same simple name as a @Nested class declared in the test class.

If the stream returned by a @TestFactory method throws an exception, the dynamic tests it has already provided now finish before the @AfterEach methods and after-each callbacks of the factory method are executed. Previously, with parallel execution, these could run while the dynamic tests were still executing.

ClassOrderer.Random and MethodOrderer.Random now log the used seed only once per launcher session.

When using @CsvSource.value[] CSV records starting with a comment character cause the test to fail. Either change commentCharacter to something else or enclose the field in quotes.

When using @CsvSource.value[] the commentCharacter must be distinct from both delimiter and quoteCharacter.

When the timeout provided to assertTimeout, assertTimeoutPreemptively and test methods annotated with @Timeout is not a positive value less than 2⁶³ nanoseconds (approximately 292 years) a PreconditionViolationException is thrown.

ExtensionContext.Namespace and ExtensionContext.Store have been deprecated in favor of org.junit.jupiter.api.store.Namespace and org.junit.jupiter.api.store.Store. In most cases, changing the Namespace and Store imports suffices to migrate.

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.

The assertTimeout, assertTimeoutPreemptively and methods annotated with @Timeout now measure the execution time with sub-millisecond precision.

Jupiter configuration parameters are documented in META-INF/junit-platform-configuration-metadata.json

The junit.jupiter.execution.parallel.config.executor-service configuration parameter now defaults to WORKER_THREAD_POOL when parallel execution is enabled.

Implementations of ClassOrderer or MethodOrderer may now access the store scoped to the enclosing launcher session via the new DiscoveryContext.getStore(…​) API. This can be used to store or cache information that is reused during test execution or later discovery phases.

New org.junit.jupiter.api.store package containing Store and Namespace interfaces which are now extended by ExtensionContext.Store and ExtensionContext.Namespace, respectively.

❓

❓

Vintage configuration parameters are documented in META-INF/junit-platform-configuration-metadata.json

Provide reachability metadata for junit-platform-engine to restore compatibility with GraalVM 25

❓

❓

❓

❓

❓

❓

❓

❓

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.