A bit more than 11 years ago GradleTest 0.5 was released. It preceded Testkit and it was born out of frustration of hard it was to test a plugin against multiple versions of Gradle. it basically used

javaexec

to run different version of Gradle against a test set. Simplistic, raw and rough around the edges it got the job done. Testkit would eventually come along and GradleTest evolved to use that under the hood, making debugging easier and simplify setup for more complex test cases. Anyhow, after that history tidbit, I am glad to announce the GradleTest 5.0.0 got released today. It comes with three main features. • Support for using custom JDKs in testing. You can create a test set which uses a JDK other than your other compatibility tests. Let's say you build your plugin against JDK11, but want to test against Gradle9, you can create a second test set where the JDK is set to 17. I_t even comes with the option to perform variant selection when it is needed. (Thanks to some tips from @Vampire)_ • Support for testing a plugin against isolated projects if the Gradle version under test is Gradle 9.7+ • Better customisation of a per-version basis. You can change behaviour depending of the Gradle version under testing including activating or silencing specific deprecation warnings, configuration cache modes and now isolation project modes. The new DSL is a good departure away from the clunky 4.0 DSL for version customisation. And it has been tested on a host Gradle version range of 7.3 to 9.7. More info here and hopefully you'll find it useful to test your own plugins. gradletest.ysb33r.org/gradletest/5.0.0/index.html