Several years ago we migrated from JUnit 4 based parameterized test classes to standard JUnit Jupiter based test classes with @ParameterizedTest methods.
However, the only reason we did that is that JUnit Jupiter did not have support for parameterized test classes.
Since JUnit Jupiter 5.13, however, there is built-in support for @ParameterizedClass.
Thus, we should migrate to @ParameterizedClass wherever feasible and/or beneficial.
Comment From: sbrannen
As a proof of concept, I migrated CronTriggerTests to @ParameterizedClass in fac8708857734c17d88e9a64a34feed40fd2f550.
The result is a much more streamlined implementation of the parameterization, and it feels more natural.
The only downside is that Gradle currently does not know how to display test results for a @ParameterizedClass.
The following screenshot shows that Gradle simply displays each test method multiple times.
Whereas, Eclipse IDE displays the tests as follows.
Comment From: sbrannen
Gradle build scans only display each test method once.
If you click on an individual test method, it then actually shows multiple executions, but it does not provide the parameterization information.
