Skip to content

Commit 176ac40

Browse files
committed
Fix formatting and polish 5.9 M1 release notes
1 parent 5df7406 commit 176ac40

File tree

1 file changed

+28
-23
lines changed

1 file changed

+28
-23
lines changed

documentation/src/docs/asciidoc/release-notes/release-notes-5.9.0-M1.adoc

Lines changed: 28 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,8 @@
55

66
*Scope:*
77

8-
* XML reports in new https://github.com/ota4j-team/open-test-reporting[Open Test Reporting] format
8+
* XML reports in new https://github.com/ota4j-team/open-test-reporting[Open Test Reporting]
9+
format
910
* Configurable cleanup mode for `@TempDir`
1011
* New `TestInstancePreConstructCallback` extension API
1112
* Reusable parameter resolution for custom extension methods via `ExecutableInvoker`
@@ -22,10 +23,11 @@ on GitHub.
2223

2324
==== Bug Fixes
2425

25-
* Fix handling of global post-discovery filters that apply to `@Suite` classes.
26-
* Since Turkish language has special characters as 'ı' and 'İ', the uppercase conversion on
27-
`DefaultParallelExecutionConfigurationStrategy#getStrategy` was causing all test to finish
28-
with exit code -1. That has been fixed by using Root locale instead of default one.
26+
* Fixed handling of global post-discovery filters that apply to `@Suite` classes.
27+
* Since the Turkish language has special characters such as 'ı' and 'İ', the uppercase
28+
conversion in `DefaultParallelExecutionConfigurationStrategy#getStrategy` previously
29+
caused all tests to finish with exit code -1. This has been fixed by using the root
30+
locale instead of the default one.
2931

3032
==== Deprecations and Breaking Changes
3133

@@ -34,31 +36,32 @@ on GitHub.
3436

3537
==== New Features and Improvements
3638

37-
* Add support for https://github.com/ota4j-team/open-test-reporting[Open Test Reporting]
39+
* Support for the https://github.com/ota4j-team/open-test-reporting[Open Test Reporting]
3840
format which supports all features of the JUnit Platform such as hierarchical test
3941
structures, display names, tags, etc. Please refer to the
4042
<<../user-guide/index.adoc#junit-platform-reporting-open-test-reporting, User Guide>>
4143
for instructions on how to enable such reports in your build.
4244
* `ConfigurationParameters` has a new `keySet()` method which allows you to retrieve all
4345
configuration parameter keys.
4446
* New `IterationSelector` for selecting a subset of a test's or container's iterations.
45-
* `ParallelExecutionConfiguration` allows configuring the "saturate" predicate of the
47+
* `ParallelExecutionConfiguration` allows configuring the `saturate` predicate of the
4648
`ForkJoinPool` used for parallel test execution.
4749
* JUnit OSGi bundles now contain `engine` and `launcher` requirements ensuring that at
4850
resolution time a fully running set of dependencies is calculated, avoiding the need for
4951
these to be manually specified.
5052
* JUnit Platform Standalone Console JAR now also includes the JUnit Platform Suite Engine.
5153
* New `failIfNoTests` attribute added to `@Suite`. This will fail the suite if no tests
52-
were discovered.
53-
* `ConsoleLauncher`'s output color can now be customized. The option `--single-color` will
54-
apply a built-in monochrome style, while `--color-palette` will accept a properties file.
55-
See the <<../user-guide/index.adoc#running-tests-console-launcher-color-customization,
54+
are discovered.
55+
* The output color for the `ConsoleLauncher` can now be customized. The option
56+
`--single-color` will apply a built-in monochrome style, while `--color-palette` will
57+
accept a properties file. See the
58+
<<../user-guide/index.adoc#running-tests-console-launcher-color-customization,
5659
User Guide>> for details.
57-
* `ConsoleLauncher`'s default theme is now determined by the charset reported by the system
58-
console on Java 17 and later.
59-
* New `--list-engines` option added to the `ConsoleLauncher` displaying all registered test
60-
engine implementations.
61-
* Configuring include `EngineFilters` that do not match any registered `TestEngine`
60+
* The default theme for the `ConsoleLauncher` is now determined by the charset reported by
61+
the system console on Java 17 and later.
62+
* New `--list-engines` option added to the `ConsoleLauncher` which displays all registered
63+
test engine implementations.
64+
* Configuring included `EngineFilters` that do not match any registered `TestEngine`
6265
results in an error to avoid misconfiguration – for example, due to typos.
6366

6467

@@ -67,10 +70,11 @@ on GitHub.
6770

6871
==== Bug Fixes
6972

70-
* Only retry deleting directories when cleaning up `@TempDir` once.
71-
* Since Turkish language has special characters as 'ı' and 'İ', the uppercase conversion on
72-
`DefaultParallelExecutionConfigurationStrategy#getStrategy` was causing all test to finish
73-
with exit code -1. That has been fixed by using Root locale instead of default one.
73+
* When cleaning up a `@TempDir`, only one retry attempt will be made to delete directories.
74+
* Since the Turkish language has special characters such as 'ı' and 'İ', the uppercase
75+
conversion in `DefaultParallelExecutionConfigurationStrategy#getStrategy` previously
76+
caused all tests to finish with exit code -1. This has been fixed by using the root
77+
locale instead of the default one.
7478

7579
==== Deprecations and Breaking Changes
7680

@@ -90,13 +94,14 @@ on GitHub.
9094
* New `TestInstancePreConstructCallback` extension API that is called prior to test
9195
instance construction – symmetric to the existing `TestInstancePreDestroyCallback`
9296
extension API.
93-
* Extensions can now leverage registered `ParameterResolvers` when invoking methods and
94-
constructors via the new `ExecutableInvoker` available in the `ExtensionContext`.
97+
* Extensions can now leverage registered `ParameterResolver` extensions when invoking
98+
methods and constructors via the new `ExecutableInvoker` API available in the
99+
`ExtensionContext`.
95100
* A subset of the invocations of parameterized or dynamic tests can now be selected via
96101
the new `IterationSelector` discovery selector when launching the JUnit Platform.
97102
* `JAVA_19` has been added to the `JRE` enum for use with JRE-based execution conditions.
98103
* `@MethodSource` factory methods can now accept arguments resolved by registered
99-
`ParameterResolver`.
104+
`ParameterResolver` extensions.
100105

101106

102107
[[release-notes-5.9.0-M1-junit-vintage]]

0 commit comments

Comments
 (0)