Support test coverage analysis when running tests selectively

Metadata

Source

tuist/tuist #8820

Updated

Jun 11, 2026

Domains

CLI

Details

Why is this needed?

Test coverage tools assume you always run all the tests. However, that’s not the case with selective testing, where only a subset of them run. Therefore, there’s value in us providing coverage data taking into account the tests that have been selected.

Flights

Investigate, reproduce, or fix this item in an isolated repository. Each Flight preserves its outcome and agent session.

New Flights are paused Configure model inference, GitHub, and a sandbox provider to start another Flight. Existing results remain available below.

No Flights yet

Start a Flight and preserve its objective, outcome, and session here.

Comments

L

linear[bot] Dec 3, 2025

T

tejassharma96 Dec 3, 2025

One other thing that would be great to have with this coverage analysis would be PR impact reports on coverage, so we can see how the changes in a branch affected the coverage of each module it touches (which is very difficult to reason about with selective testing 😅)

F

fortmarek Dec 3, 2025

we have a dashboard that tracks coverage per module per branch but main is the only one that provides “true” coverage for the whole module since we run tests for the entire module there. prior to selective testing we also had a bot that would hit the metrics server and grab the diff to main and post it as a comment, but that’s useless ever since enabling selective testing.