<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=6284) </details> <!--IssueSummary end--> <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> ### Problem to solve As a team lead, I want my project to have/enforce a minimum amount of test coverage, so that I can focus on larger issues for the project like code quality, are we delivering value to customers, etc. <!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." --> ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) - Or a maintainer sets the minimum test coverage percentage an MR must have to be merged. * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) - will see the alert if their change will decrease the test coverage below the project minimum. ### User experience goal <!-- What is the single user experience workflow this problem addresses? For example, "The user should be able to use the UI/API/.gitlab-ci.yml with GitLab to <perform a specific task>" https://about.gitlab.com/handbook/engineering/ux/ux-research-training/user-story-mapping/ --> * The Maintainer should be able to use the GitLab UI to set a minimum test coverage % for a project. * TBD - Is this the average percentage or by regex set in the settings? * A developer will see a message on the Merge Request page ( in the existing treatment shown below OR something new?) if the project will be below the set test coverage with the MR merged.  ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> * Add interface to the CI/CD settings to set an optional minimum test coverage % (average and/or by regex setup) * Ensure that maintainers can override this requirement * Add to the existing interface or new interface on the MR page an alert about why a merge is blocked when test coverage would be below the threshold after the merge. * Update documentation for CI/CD settings and MR page * Track the number of projects with a set threshold ### Further details <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. --> Since we're able to show test coverage in the MR widget (https://docs.gitlab.com/ee/user/project/pipelines/settings.html), we should consider enabling test coverage enforcement before accepting a merge request. ### Permissions and Security Only Maintainers and Owners will be able to set the threshold for a project. ### Documentation * Update documentation for CI/CD settings * Update documentation for MR ### Availability & Testing * It will be very important to ensure that an MR can still be merged by a project maintainer/owner similar to [Security approvals](https://docs.gitlab.com/ee/user/application_security/#enabling-security-approvals-within-a-project) <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? Within 90 days of launch/tracking availability 100 projects have implemented a minimum test coverage threshold. <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. Create tracking issue using the the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md --> ### What is the type of buyer? The user who cares about this is the Team Lead but is likely a ~"GitLab Core" tiered feature. ### Is this a cross-stage feature? Yes, this involves the ~"devops::create" stage who works on the MR page. <!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> ### Links / references [Coverage documentation](https://docs.gitlab.com/ee/ci/yaml/README.html#coverage)