Repository navigation
docs: document regression test tracking - #621
Conversation
Added guidelines for regression test tracking in bug-fix PRs.
Katrien De Graeve (katriendg)
left a comment
There was a problem hiding this comment.
Thank you Daniel (@Danielweng0902) for picking this one up, your focused work on the Documentation update of the issue looks good. The ref to the issue without fully closing it is the right approach so we can tackle CI in a subsequent commit.
I already created the label in the system.
Good to merge from my side.
Updated the date and added a requirement for bug-fix PRs to have a 'bug' label at merge time for better tracking.
|
Addressed both comments in the latest commit. Thanks! |
📚 Documentation Health ReportGenerated on: 2026-06-22 17:22:48 UTC 📈 Documentation Statistics
🏗️ Three-Tree Architecture Status
🔍 Quality Metrics
This report is automatically generated by the Documentation Automation workflow. |
📚 Documentation Health ReportGenerated on: 2026-06-22 17:26:18 UTC 📈 Documentation Statistics
🏗️ Three-Tree Architecture Status
🔍 Quality Metrics
This report is automatically generated by the Documentation Automation workflow. |
📚 Documentation Health ReportGenerated on: 2026-06-22 17:51:45 UTC 📈 Documentation Statistics
🏗️ Three-Tree Architecture Status
🔍 Quality Metrics
This report is automatically generated by the Documentation Automation workflow. |
78bcd91
into
microsoft:main
Description
Adds a Regression Test Tracking section to the existing Test Policy so bug-fix PRs document regression coverage consistently.
Related Issue
Refs #176
Type of Change
Implementation Details
regression-testlabel as the tracking signal for PRs that include regression coverage.Testing Performed
Validation Steps
Review the rendered Markdown in
docs/contributing/testing-validation.md.Checklist