Visual indicator MR should not be merged because it decreases coverage
Problem to solve
As a developer authoring an MR, I want to see in GitLab if the test coverage meets the project/team goal, so that I can ensure my change meets team norms without leaving the tool.
Intended users
User experience goal
The user should be able to use the UI and see that an MR should not be merged in the UI if the new coverage will decrease. This iteration/issue WILL NOT block the Merge based solely on this criteria.
Proposal
Design - In Progress
Design will be added after it is finalized in this separate issue.
- If a project is setup to block / warn on test coverage decrease (issue) add a warning to the MR beyond what is there to show coverage change on the pipeline widget.
Further details
Permissions and Security
Utilize permissions and security already setup for MRs within the project.
Documentation
None.
Availability & Testing
Available Tier
- Free
What does success look like, and how can we measure that?
Success Metrics
- At least 10 projects are setup for blocking/warning MRs within 30 days of release of this on gitlab.com (future issue)
Acceptance Criteria
- Alert shows when expected (shown on coverage decrease, does not show on coverage stay and increase)
What is the type of buyer?
Developer
Is this a cross-stage feature?
This will display on the MR page which is a devopscreate page
Links / references
Second step of the epic Enforce Code Coverage for merge
Edited by James Heimbuck