CI teams piece together complete test and coverage reports
In monorepos and sharded CI, test and coverage outputs are split by spec, project, or job, so teams struggle to get one complete report. Pipelines may overwrite earlier results, summarize only one file, or require manual artifact downloads and merge scripts; format gaps can also make dashboard integration harder. Aggregation will not solve every related request, such as adding coverage instrumentation to a test workflow, but it addresses the recurring reporting bottleneck.
For developers and test teams using monorepos or sharded CI. Mentioned from Aug 2016 to Mar 2024 on GitHub.
19 different people described this problem in 8 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.4/10
- Frequency
- 10.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
To get around this, we can merge all the files using ReportGenerator. This is what worked for me: 1. (Optional) If the code coverage is coming from different jobs, publish the coverage files as artifacts and then have a later job download all the artifacts
Produced coverage report in coverage/lcov.info only contains results for the last run code coverage
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 18 more quotes from people who have this problem
- Current workarounds, existing solutions and risks