From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

&gt;  The alternative is setting `org.gradle.jvmargs=...` in the gradle.properties of every test project
This is effectively what Gradle <https://github.com/gradle/kotlin-dsl-samples/pull/832/files|did themselves> to remove usage of the internal `DefaultGradleRunner` class.

&gt; that's annoying/repetitive
Can you refactor the test classes to use some common helper base classes that make things less painful?

ahh right, thanks, I misread the comment in the GitHub issue

yeah, I could add a helper function. But then that's more work than just casting to DefaultGraderRunner, and the result seems to be the same, so I'm not sure why Gradle wants to hide it.

It may be more work, but I've found it to be a useful way to uniformly add capabilities to my Gradle tests. The other benefit is that you no longer rely on Gradle internals that may or may not remain useable in the future. At least with the supported API you have more confidence that it won't disappear without warning.