[DiscoveryTestClassesTask] Task that discovers testClasses in spock and junit-jupiter test engines

[crogoz]

Before this PR

After this PR

FLUP for https://pl.ntr/2ye. We can now auto-discover the testClasesFiles in a repo using a DiscoveryTestClassesTask task. Introducing 2 tasks:

1. discoverGradlePluginTests discovers GradlePluginTests annotated test classes. This will be used by the Configuration cache enablement migration to discover the tests that need to be annotated with @DisabledConfigurationCache.
2. discoverGroovyTestClassesToMigrate discovers the groovy test classes that extend IntegrationSpec, IntegrationTeskKitSpec excluding the ConfigurationCacheSpec tests. This will be used by the excavator to discover the groovy tests that need to be migrated to the new junit framework.

==COMMIT_MSG==
[DiscoveryTestClassesTask] Task that discovers testClasses in spock and junit-jupiter test engines
==COMMIT_MSG==

Possible downsides?

[changelog-app]

Generate changelog in changelog/@unreleased

Type (Select exactly one)

• Feature (Adding new functionality)
• Improvement (Improving existing functionality)
• Fix (Fixing an issue with existing functionality)
• Break (Creating a new major version by breaking public APIs)
• Deprecation (Removing functionality in a non-breaking way)
• Migration (Automatically moving data/functionality to a new system)

Description

[DiscoveryTestClassesTask] Task that discovers testClasses in spock and junit-jupiter test engines

Check the box to generate changelog(s)

• Generate changelog entry

[changelog-app]

✅ Successfully generated changelog entry!

Need to regenerate?

Simply interact with the changelog bot comment again to regenerate these entries.

---

📋Changelog Preview

💡 Improvements

• [DiscoveryTestClassesTask] Task that discovers testClasses in spock and junit-jupiter test engines (#297)

[felixdesouza]

I think we want to capture integrationTest as well? That said, there aren't that many of them internally.

[crogoz]

I don't think this project is wiring in other places other sourceSets besides the test one. Should we add it as a FLUP ?

[felixdesouza]

how are you capturing the classes that are discover-tests-cli ?

I think it's a little weird to put the runtimeClasspath on here.

We should probably make a configuration that contains just the discovery-tests-cli module and union that with the test classpath.

We should probably lock it as well since we wouldn't want it to clash - although we can probably hold off on this part until we see any issues.

[crogoz]

I actually don't need this anymore - as the "testImplementation" of the project already has the "discovery-tests-cli" here: https://github.com/palantir/gradle-plugin-testing/pull/297/files#diff-ca7ede7b34d2580d6fdb25b3707c5007eb08095357c26ab8c22bcb48236f2b85R232. Let me know if you prefer to have a separate config for this though