JUnit Release Notes

Discontinue junit-platform-suite-commons which is now integrated into junit-platform-suite.

Deprecate Launcher.execute(TestPlan, TestExecutionListener[]) and Launcher.execute(LauncherDiscoveryRequest, TestExecutionListener[]) in favor of Launcher.execute(LauncherExecutionRequest)

ConversionSupport now converts String to Locale using the IETF BCP 47 language tag format supported by the Locale.forLanguageTag(String) factory method instead of the format used by the deprecated Locale(String) constructor.

Deprecate getOrComputeIfAbsent(…​) methods in NamespacedHierarchicalStore in favor of the new computeIfAbsent(…​) methods.

Setting an invalid value for one of the following enum-based configuration parameters now causes test discovery to fail:

Introduce new Launcher.execute(LauncherExecutionRequest) API with corresponding LauncherExecutionRequestBuilder to enable the addition of parameters to test executions without additional overloads of execute(…​).

Introduce LauncherDiscoveryRequestBuilder.forExecution() method as a convenience method for constructing a LauncherExecutionRequest that contains a LauncherDiscoveryRequest.

Introduce support for cancelling a running test execution via a CancellationToken passed to the Launcher as part of a LauncherExecutionRequest and from there to all registered test engines. Please refer to the User Guide for details and a usage example.

Passing the --fail-fast option to the execute subcommand of the ConsoleLauncher now causes test execution to be cancelled after the first failed test.

Provide cancellation support for implementations of HierarchicalTestEngine such as JUnit Jupiter, Spock, and Cucumber.

Provide cancellation support for the @Suite test engine.

Introduce TestTask.getTestDescriptor() method for use in HierarchicalTestExecutorService implementations.

Introduce computeIfAbsent(…​) methods in NamespacedHierarchicalStore to simplify working with non-nullable types.

Change the return type of the provideTestTemplateInvocationContexts(ExtensionContext) method in the TestTemplateInvocationContextProvider interface from Stream<TestTemplateInvocationContext> to Stream<? extends TestTemplateInvocationContext>.

Remove support for the junit.jupiter.params.arguments.conversion.locale.format configuration parameter. Locale conversions are now always performed using the IETF BCP 47 language tag format supported by the Locale.forLanguageTag(String) factory method.

Deprecate getOrComputeIfAbsent(…​) methods in ExtensionContext.Store in favor of the new computeIfAbsent(…​) methods.

Setting an invalid value for one of the following enum-based configuration parameters now causes test discovery or execution to fail:

Display names for @ParameterizedClass and @ParameterizedTest now consistently style name-value pairs for arguments using name = value formatting – for example, fruit = apple instead of fruit=apple.

Reason strings supplied to ConditionEvaluationResult APIs are now officially declared as @Nullable.

Introduce computeIfAbsent(…​) methods in ExtensionContext.Store to simplify working with non-nullable types.

Provide cancellation support for the Vintage test engine.

Minimum required Java version is now 17.

Minimum required Kotlin version is now 2.2.

Platform artifacts now use the same version number as Jupiter and Vintage artifacts.

All JUnit modules now use JSpecify nullability annotations to indicate which method parameters, return types, etc. can be null.

Remove deprecated support for running the ConsoleLauncher without specifying a subcommand.

Remove support for deprecated non-conventional ConsoleLauncher options such as --h (rather than -h) or -help (rather than --help).

The junit-platform-runner module that provided the JUnit 4 based JUnitPlatform runner has been discontinued.

The junit-platform-jfr module that provided custom Java Flight Recorder (JFR) events for test discovery and execution has been discontinued. Instead, the functionality is now available directly in junit-platform-launcher without requiring an additional dependency.

Support for Maven Surefire/Failsafe versions less than 3.0.0 has been dropped.

The following deprecated APIs have been removed:

Support for "legacy semantics" for field and method searches that used to be configurable via the junit.platform.reflection.search.useLegacySemantics system property has been removed. JUnit now always adheres to standard Java semantics regarding whether a given field or method is visible or overridden according to the rules of the Java language.

The type bounds of the following methods have been changed to be more flexible and allow nullable and non-nullable types:

The following deprecated APIs have been removed:

The deprecated junit.jupiter.tempdir.scope configuration parameter is no longer supported.

The JRE enum constants for JAVA_8 to JAVA_16 have been deprecated because they can no longer be used at runtime since JAVA_17 is the new baseline. Please also manually update any values used with the minVersion and maxVersion attributes in @EnabledForJreRange and @DisabledForJreRange or the versions attributes in @EnabledOnJre and @DisabledOnJre to ensure that you are no longer declaring version values less than 17.

@EnabledForJreRange and @DisabledForJreRange now use JAVA_17 as their default min value.

The contracts for the Executable parameters of Kotlin-specific assertTimeout functions were changed from callsInPlace(executable, EXACTLY_ONCE) to callsInPlace(executable, AT_MOST_ONCE) which might result in compilation errors.

As a result of migrating from univocity-parsers to FastCSV for @CsvSource and @CsvFileSource, root causes and messages of exceptions thrown for malformed CSV input may differ in some cases. While the overall parsing behavior remains consistent, this may affect custom error handling that relies on specific exception types or messages.

The lineSeparator attribute in @CsvFileSource has been removed. The line separator is now automatically detected, meaning that any of \r, \n, or \r\n is treated as a line separator.

Attributes such as ignoreLeadingAndTrailingWhitespace, nullValues, and others in @CsvSource and @CsvFileSource now apply to header fields as well as to regular fields.

Extra characters after a closing quote are no longer allowed in @CsvSource and @CsvFileSource. For example, if a single quote is used as the quote character, the following CSV value 'foo’INVALID,'bar' will now cause an exception to be thrown. This helps ensure that malformed input is not silently accepted or misinterpreted.

The junit-jupiter-migrationsupport artifact and its contained classes are now deprecated and will be removed in the next major version.

The type bounds of the following methods have been changed to be more flexible and allow nullable and non-nullable types:

Kotlin’s suspend modifier may now be applied to test and lifecycle methods.

The Arguments interface for parameterized tests is now officially a @FunctionalInterface.

The implementation of @CsvSource and @CsvFileSource has been migrated from the no longer maintained univocity-parsers to FastCSV. This improves the consistency of CSV input handling, including for malformed entries, and provides better error reporting and overall performance.

The JUnit Vintage engine is now deprecated and will report an INFO level discovery issue when it finds at least one JUnit 4 test class. For now, the intent of the deprecation is not to signal removal in the next major version but to clarify the intended purpose of the engine. It should only be used temporarily while migrating tests to JUnit Jupiter or another testing framework with native JUnit Platform support.

Remove java.* packages from Import-Package headers in all jar manifests to maximize compatibility with older OSGi runtimes.

ClasspathResourceSelector no longer allows to be constructed with a resource name that is blank after removing the leading slash.

PackageSource.from(String) now allows to be constructed with an empty string to indicate the default package.

Log only once per implementation type for CloseableResource implementations that do not implement AutoCloseable to avoid flooding console output with this warning.

All experimental APIs have been promoted to maintained to indicate that they won’t be removed in any future 5.x release.

Fix regression that caused top-level and static member classes annotated with @Nested to no longer be executed because they caused a discovery issue to be reported.

Stop reporting discovery issues for composed annotation classes that are meta-annotated with @Nested.

Stop reporting discovery issues for DefaultImpls classes generated by the Kotlin compiler for interfaces with non-abstract test methods.

When a customReason is supplied along with a null value for the default reason to ConditionEvaluationResult.disabled(String, String), the resulting reason is now "my custom reason" instead of "null ==> my custom reason".

A blank reason supplied to a ConditionEvaluationResult factory method is now treated the same as a null reason, resulting in an empty Optional returned from ConditionEvaluationResult.getReason().

The Javadoc for factory methods in ConditionEvaluationResult now explicitly states that both null and blank values are supported for reason strings and that such values will result in an empty Optional returned from ConditionEvaluationResult.getReason().

Improve message of discovery issues reported for ineffective @Order annotations.

If Git information is included in the Open Test Reporting XML format (see below), any credentials that may be configured as part the remote.origin.url setting in Git were previously written to the originUrl attribute of <git:repository> elements. For example, when cloning a GitHub repository using a URL like https://username:[email protected]/organization/repository.git, both username and password were included in the XML report. Since a report which includes this information may be shared, published, or archived (for example, on a CI server), this was reported as a potential security vulnerability (CVE-2025-53103). Any credentials are now replaced with *** before writing them to the XML report.

Including information about the Git repository (such as the commit hash and branch name) in the Open Test Reporting XML format is now an opt-in feature that can be enabled via a configuration parameter. Please refer to the User Guide for details.

Stop reporting discovery issues for cyclic inner class hierarchies not annotated with @Nested.

Stop reporting discovery issues for abstract inner classes that contain test methods but are not annotated with @Nested.

Stop reporting discovery issues for abstract test methods. Although they will not be executed, it is a valid pattern to annotate them with @Test for documentation purposes and override them in subclasses while re-declaring the @Test annotation.

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

The 5.13.0 release introduced a regression regarding the execution order in test classes containing both test methods and @Nested test classes. When classpath scanning was used during test discovery — for example, when resolving a package selector for a @Suite class — test methods in @Nested classes were executed before test methods in their enclosing class. This undesired change in behavior has now been reverted so that tests in @Nested test classes are always executed after tests in enclosing test classes again.

Fix support for AnnotationBasedArgumentsProvider implementations that override the deprecated provideArguments(ExtensionContext, Annotation) method.

The JUnit feature in GraalVM Native Build Tools (NBT) has been rewritten to no longer require JUnit classes to be initialized at build time when running on JDK 22 and later. Therefore, JUnit’s JARs no longer ship with native-image.properties files that contain --initialize-at-build-time options (introduced in 5.12.0). Please update to the most recent version of GraalVM Native Build Tools prior to upgrading to this version of JUnit. Please refer to the Upgrade Instructions in the wiki for details if you’re on NBT 0.10.x or earlier.

Notify LauncherDiscoveryListener implementation registered via LaucherConfig or on the Launcher of selectorProcessed events.

Reintroduce support for JVM shutdown hooks when using the -cp/--classpath option of the ConsoleLauncher. Prior to this release, the created class loader was closed prior to JVM shutdown hooks being invoked, which caused hooks to fail with a ClassNotFoundException when loading classes during shutdown.

Fix support of --uid and --select-unique-id options in the console launcher.

Introduce a mechanism for TestEngine implementations to report issues encountered during test discovery. If an engine reports a DiscoveryIssue with a Severity equal to or higher than a configurable critical severity, its tests will not be executed. Instead, the engine will be reported as failed during execution with a failure message listing all critical issues. Non-critical issues will be logged but will not prevent the engine from executing its tests. The critical severity can be configured via a new configuration parameter and, currently, defaults to ERROR. Please refer to the User Guide for details.

Start reporting discovery issues for problematic @Suite classes:

Introduce resource management mechanism that allows preparing and sharing state across executions or test engines via stores that are scoped to a LauncherSession or ExecutionRequest. The Jupiter API uses these stores as ancestors to the Store instances accessible via ExtensionContext and provides a new method to access them directly. Please refer to the User Guide for examples of managing session-scoped and request-scoped resources.

New ConsoleLauncher options --redirect-stdout and --redirect-stderr for redirecting stdout and stderr output streams to files.

Add TestDescriptor.Visitor.composite(List) factory method for creating a composite visitor that delegates to the given visitors in order.

Introduce test discovery support in EngineTestKit to ease testing for discovery issues produced by a TestEngine. Please refer to the User Guide for details.

Make validation of including EngineFilters more strict to avoid misconfiguration, for example, due to typos. Prior to this release, an exception was only thrown when none of a filter’s included IDs matched any engine. Now, an exception is thrown if at least one included ID across all filters did not match any engine.

If the autoCloseArguments attribute in @ParameterizedTest is set to true, all arguments returned by registered ArgumentsProvider implementations are now closed even if the test method declares fewer parameters.

AutoCloseable arguments returned by an ArgumentsProvider are now closed even if they are wrapped with Named.

AutoCloseable arguments returned by an ArgumentsProvider are now closed even if a failure happens prior to invoking the parameterized method.

Validate all versions specified in @EnabledOnJre and @DisabledOnJre annotations.

New @ClassTemplate annotation and ClassTemplateInvocationContextProvider API that allow declaring a top-level or @Nested test class as a template to be invoked multiple times. This may be used, for example, to inject different parameters to be used by all tests in the class template or to set up each invocation of the class template differently. Please refer to the User Guide for details.

New BeforeClassTemplateInvocationCallback and AfterClassTemplateInvocationCallback extension callback interfaces allow implementing extensions that are invoked before and after each invocation of a class template.

New @ParameterizedClass support that builds on @ClassTemplate and allows declaring a top-level or @Nested test class as a parameterized test class to be invoked multiple times with different arguments. The same @…​Source annotations supported with @ParameterizedTest may be used to provide arguments via constructor or field injection. Please refer to the User Guide for details.

New @ParameterizedClass-specific @BeforeParameterizedClassInvocation/@AfterParameterizedClassInvocation lifecycle methods that are invoked once before/after each invocation of the parameterized class.

Provide access to the parameters and resolved arguments of a @ParameterizedTest or @ParameterizedClass by storing ParameterInfo in the ExtensionContext.Store for retrieval by other extensions. Please refer to the Javadoc for details.

New @SentenceFragment annotation which allows one to supply custom text for individual sentence fragments when using the IndicativeSentences DisplayNameGenerator. See the updated documentation in the User Guide for an example.

New TestTemplateInvocationContext.prepareInvocation(ExtensionContext) callback method which allows extensions to prepare the ExtensionContext before the test template method is invoked. This may be used, for example, to store entries in the ExtensionContext.Store to benefit from its cleanup support or for retrieval by other extensions.

Start reporting discovery issues for potentially problematic test classes:

By default, AutoCloseable objects put into ExtensionContext.Store are now treated like instances of CloseableResource (which has been deprecated) and are closed automatically when the store is closed at the end of the test lifecycle. It’s possible to revert to the old behavior via a configuration parameter. Please also see the migration note for third-party extensions wanting to support both JUnit 5.13 and earlier versions.

java.util.Locale arguments are now converted according to the IETF BCP 47 language tag format. See the User Guide for details.

Avoid reporting potentially misleading validation exception for @ParameterizedClass test classes and @ParameterizedTest methods as suppressed exception for earlier failures.

Add support for Kotlin Sequence to @MethodSource, @FieldSource, and @TestFactory.

Allow publishing files to an existing directory via TestReporter and ExtensionContext, for example, when re-running a test class.