This message was deleted.

My thought is that I would have 3 styles of plugins:

myApp.codeCoverage.aggregator
myApp.codeCoverage.library.android // for android subprojects
myApp.codeCoverage.library.java // for java (non-android) subprojects

myApp.codeCoverage.library.android

would create tasks that expose 3 types of code coverage values - jvm tests, android tests, and merged jvm/android test coverage.

myApp.codeCoverage.library.java

would expose a task to create code coverage reports for jvm tests. Though I might want to explore a different report for different test suites in the future. `myApp.codeCoverage.aggregator`’s job would be to take the above information and merge it to create a unified report across multiple subprojects. However, I would like this to be dynamic. I might have 5 subprojects that make up one feature, and I would like to have a single coverage report for just those 5 subprojects. What is the idiomatic gradle way to achieve this?

Does the jacoco report aggregation do what you want? https://docs.gradle.org/7.4-rc-2/userguide/jacoco_report_aggregation_plugin.html

it might (I’m not sure how compatible it is with Android at the moment). What I would be designing would be a wrapper around it

kover has this ootb

I’m a bit hesitant to adopt

Kover

given its design issues around project isolation. Created Project Isolation support