Migrate to `@ParameterizedClass` where feasible

[sbrannen]

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.

[sbrannen]

As a proof of concept, I migrated CronTriggerTests to @ParameterizedClass in fac8708.

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.

[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.

[tresat]

Hi there! I think you'll be happy to see some of the improvements we have scheduled for Gradle 9.3.0, coming in just a few weeks.

You can find a preview of the release notes here. I believe this addresses your exact concerns.

[octylFractal]

To elaborate on this, with Gradle 9.3.0, given the following test class:

@ParameterizedClass
@ValueSource(strings = { "one", "two" })
public class ParamClass {
    private final String value;

    public ParamClass(String value) {
        this.value = value;
    }

    @Test
    public void sayValue() {
        System.out.println("Value: " + value);
    }
}

You can expect the following output in the local HTML report:

The Build Scan output is not affected, but we plan to improve on this in the future.

[sbrannen]

Hi there! I think you'll be happy to see some of the improvements we have scheduled for Gradle 9.3.0, coming in just a few weeks.

That's excellent news! 👏

You can find a preview of the release notes here. I believe this addresses your exact concerns.

I get a 404 for that link.

Can you perhaps provided an undated link?

[sbrannen]

Hi @octylFractal,

To elaborate on this, with Gradle 9.3.0, given the following test class:

You can expect the following output in the local HTML report:

Awesome!

That indeed looks very promising.

Thanks for sharing the screenshot.

We're looking forward to Gradle 9.3. 🚀

The Build Scan output is not affected, but we plan to improve on this in the future.

That would be warmly welcomed.

Cheers!

[tresat]

I get a 404 for that link.

Can you perhaps provided an undated link?

Sorry, the branch got merged. Try here.