regression-suite

To map regression test coverage to GDD acceptance criteria, you audit the tests directory and cross-reference it against your design document's critical paths. This generates a coverage report classifying each criterion as covered, partial, missing, or exempt.

To prevent fixed bugs from silently returning in CI release gates, you verify closed bugs against your test manifest and flag missing regression tests. This ensures recurring issues are automatically caught before release.

Coverage drift detection in sprint workflows is the process of identifying new systems, completed stories, and stale test manifests that indicate regression coverage is falling behind the evolving critical paths.

To audit missing regression tests for recently fixed bugs, you scan closed bug reports and cross-reference them with your test inventory. This flags fixed issues that lack corresponding regression tests to catch future recurrences.

Yes, you need a curated test manifest like tests/regression-suite.md to maintain critical path stability. It serves as the authoritative list of regression coverage, enabling accurate gap analysis and drift detection during audits.