Show all coverage values in MR when only select jobs run
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
GitLab enables users to parse code coverage values for display within a pipeline which is a great way to see how a change will impact the code coverage value.
If you use rules:changes and have multiple code coverage values, coverage of a branch will be the coverage of the changed module in the commit only, not the average of all modules. For example if a project has two coverage values and a commit has changes in only one module the result can be a misleading value. A project with a 50% coverage value in ruby and 90% coverage value in javascript would average 70% which is the expected value in the pipeline, not ~50% or ~90% for a change on only one of those modules respectively.
Intended users
Further details
Use Cases
- A change is made only to Frontend code, say javascript, that has a much lower code coverage value than the overall project and custom scripting blocks the change because of lowered overall test coverage. Now a developer without much experience outside javascript is making a "safe change" in another file unrelated to their change just to make the pipeline get a good value.
Proposal
The code coverage values are already available and parsed for the code coverage badges on a project. Let's use that to show overall coverage if possible.