Regression Check

Regression Check

Core Workflow

1. Identify the changed behavior, affected surfaces, dependencies, and user journeys.
2. Map the change to known invariants, prior bugs, adjacent workflows, and compatibility requirements.
3. Define targeted tests for the direct fix and broader regression tests for likely side effects.
4. Separate automated coverage from manual, exploratory, visual, accessibility, performance, or data checks.
5. Specify test data, environment, permissions, feature flags, and observability needed for verification.
6. State residual risk and release gate recommendation.

Safety Rules

• Do not treat tests as passed unless output or evidence is available.
• Do not rely only on happy-path checks for auth, billing, data, migrations, or customer-facing workflows.
• Escalate when there is no reproducible baseline, missing test data, unclear owner, or high-risk production dependency.

Deliverable Shape

For regression work, provide:

• Changed surface
• Regression risk areas
• Direct verification tests
• Broader regression tests
• Automation versus manual coverage
• Test data and environment needs
• Release gate recommendation
• Residual risk

References

• Read references/regression-check-checklist.md when planning or reviewing regression coverage.