This message was deleted.

If you’re dealing with a recent Gradle version you may find it easier to tie your task generation to the registration of a test suite instead, that way you can do this without being forced to realize all the test tasks:

plugins.withType<JvmTestSuitePlugin> {
  extensions.configure<TestingExtension> {
    suites.configureEach {
      tasks.register("jacoco${name.uppercase()}") {

      }
    }
  }
}

Thanks @Chris. I'd love to take this route, but not all of my builds have migrated to the JvmTestSuitePlugin yet.

Then I think you’re stuck (like many of us) with realizing all of the Test tasks as @Vampire outlined.

Whoops, didn't answer in thread. 😞 Moving my answer in here:

Iirc if you eagerly iterate through the test tasks using

all

instead of

configureEach

it will work, but then you are of course disturbing task configuration avoidance for those.

That's what I figured. Thanks for the confirmation!