Published on Oct 03, 2022
A number of bugs have been fixed in JUnit 5.9, and a number of new features have been introduced, such as the ability to keep temporary files after a test has been executed. When running in a GraalVM Native Image, new annotations allow you to enable or disable specific tests. The Open Testing Reporting format is now used to store XML reports.
With JUnit 5.4, the @TempDir annotation allows the automated creation and deletion of files during unit testing.
JUnit now supports the following cleanup policies for the @TempDir annotation: ALWAYS, DEFAULT, NEVER, and ON_SUCCES. The default cleanup policy is CleanupMode.ALWAYS
Moving forward, XML reports will be stored in the Open Testing Reporting format, which is independent of any testing framework or programming language. This new test result format makes it easier for tool developers to parse test reports without having to write parsers for each test framework with its own test result format.
IterationSelector allows users to select specific iterations for parameterized tests in an IDE. In current IDEs, such as IntelliJ, a green arrow indicates the possibility of rerunning the entire test with all parameters set
The new version of JUnit fixes a number of bugs and introduces a number of new features, including the ability to keep temporary files after tests are executed. GraalVM Native Images now support annotations that enable or disable specific tests. Reports are now stored in the Open Testing Reporting format in XML.
By using the @TempDir annotation, introduced in JUnit 5.4, unit tests can automatically create and delete files.
JUnit now allows for specifying the cleanup policy for the @TempDir annotation via the CleanupMode enum constants: ALWAYS, DEFAULT, NEVER and ON_SUCCES.
In the future, XML reports will be stored in the Open Testing Reporting format, which is independent of any testing framework or programming language. By using the new test result format, tool developers can parse test reports more easily without having to write parsers for each test framework with its own unique test result format.
In an IDE, the newly introduced IterationSelector class allows users to select specific iterations for parameterized tests. In some IDEs, such as IntelliJ, there is a green arrow that allows you to rerun the entire test with all parameters.
JetBrains’ YouTrack issue tracker proposes to support the IterationSelector class. This suggests adding an arrow for each value of the parameterized test in order to run the test with just one parameter instead of running it with all parameters.
This is a command line Java application that runs the JUnit Platform. ANSI style output may now be modified with the argument –single-color, which only displays text attributes without color, or –color-palette=FILE, which selects a file to customize. By using the new –list-engines argument, you will be able to view all the available test engines.
