Track coverage per team in one project
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Right now it can be hard to dissect the coverage reporting when there are multiple teams that work inside a single project. We currently give project and group level reporting on code coverage in GitLab, but sometimes multiple teams work within a single project and their coverage is collected altogether.
Problem to solve
As an engineer I would like to be able to see the coverage for the files that my team is primarily responsible for in one place, so I can judge the quality and risk associated with them.
Intended users
User experience goal
Proposal
There have been several proposals for how this could be technically achieved that have been discussed, this seems the most reasonable:
- CODEOWNERS rules that have GitLab groups mapped to portions of the monorepo. These groups would represent each team. That would map a group/team to the related code paths that could enable parsing and filtering of the reports in the repository analytics reports.
Further details
Permissions and Security
Documentation
This will need a new section in the Project level Analytics page, depending on where we decide to put this information.
https://docs.gitlab.com/ee/user/analytics/repository_analytics.html
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
This is a feature contributes to value stream analytics and change management for organizations so qualifies for GitLab Ultimate