Clarify the differences in code coverage calculations features

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Problem to solve

We have 3 places within a project that calculate code coverage:

1. Coverage badge on project home page (example) - coverage of most recent pipeline or job
2. Project code coverage page (example) - most recent coverage(s) by day
3. Project quality summary code coverage (example) - most recent pipeline that ran code coverage for the default branch

#1 (closed) actually links to #2 (closed) when you want to see the full report, but I wouldn't know how those 2 connect if I didn't go to the project quality summary first.

Proposal

It may help to add descriptions in tooltips/as text to each of these to explain how they are calculated. This could also help the user understand why data wouldn't be populating.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)

Feature Usage Metrics

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.