The Tuist Gradle plugin now uploads the code coverage of your test tasks. Turn it on with coverage { enabled = true } in the tuist block of your settings.gradle.kts, or with TUIST_TEST_COVERAGE=1 for a single invocation, and the dashboard's Code Coverage page shows each commit's figure, its modules and files, and a trend for each branch.
The plugin measures your tests with JaCoCo and keeps only your repository's product code. For JUnit Platform tests, it also records which code each test ran, so when a run leaves tests out, Tuist carries their coverage forward from an earlier run instead of reporting the commit as complete. Sharded runs merge into one figure, and test tasks restored from the build cache still report their coverage.
Run ./gradlew tuistCoverageComplete once every test job of a commit has finished. See the Gradle code coverage guide to get started.