Unwanted tasks added as dependencies to JaCoCo task

In our project (using JUnit 4) we define a jacocoTestReport Gradle task:

task jacocoTestReport(type: JacocoReport, dependsOn: ["testInternalDebugUnitTest"]) {
    group = "Reporting"
    description = "Generate Jacoco coverage reports"
    reports {
        xml.enabled = true
        html.enabled = true
        xml.destination file("${buildDir}/reports/jacoco/test/jacocoTestReport.xml")
    }

    sourceDirectories.from = files([mainSrc])
    classDirectories.from = files([debugTree], [kotlinClasses])
    executionData.from = fileTree(dir: "$buildDir", includes: ["**/**/*.exec", "**/**/*.ec"])
}

And when using JUnit 4 and checking the dependency graph we see it is indeed dependent on testInternalDebugUnitTest:

:app:jacocoTestReport
\--- :app:testInternalDebugUnitTest ...

BTW, we have two flavors, Internal and Production.

When I add the JUnit 5 plugin, however, the task is now dependent on all flavors of jacocoTestReport, which are dependent on their respective flavor of unit test task:

:app:jacocoTestReport
+--- :app:jacocoTestReportInternalDebug
|    \--- :app:testInternalDebugUnitTest ...
+--- :app:jacocoTestReportInternalRelease
|    \--- :app:testInternalReleaseUnitTest ...
+--- :app:jacocoTestReportProductionDebug
|    \--- :app:testProductionDebugUnitTest ...
+--- :app:jacocoTestReportProductionRelease
|    \--- :app:testProductionReleaseUnitTest ...
\--- :app:testInternalDebugUnitTest *

Which results in our unit tests running once for each flavor combination, when we only want to run them for InternalDebug.

[mannodermaus]

I’m glad it turned out well for you in the end! Closing this ticket. 🙏

Is there any side effects of the configuration below?

The only side effect is that the variant-specific Jacoco tasks aren’t generated automatically - other than that, nothing else comes to mind. That being said, this integration with Jacoco stems from a very old requirement, before there was native support for JUnit 5 in Gradle. Now that the first-party tasks run it well, it might be time to deprecate the integration slowly…

[mannodermaus]

Glad to hear that it worked out eventually, and thanks @nuhkoca for chiming in, much appreciated! As for questions related to JUnit 5 execution performance on CI, please raise potential questions on their repo directly 🙏