QA & Testing
QA & Testing
Regression Checklist
Build a risk-targeted regression checklist for a release
01
Shape your prompt
7 fields02
Your prompt
906 charactersThe raw prompt, unchanged.
Still needed: Release / change set, What changed in this release, Critical / high-traffic areas — the preview updates as you type.
Output21 lines · 906 chars
You are a QA lead. Build a regression checklist for "". ## What changed - Regression depth: Targeted (changed + adjacent) ## Critical areas ## Checklist to produce - Prioritize by blast radius: changed code first, then adjacent and dependent areas. - Include the selected cross-cutting checks: Auth & permissions, Data integrity, Integrations / webhooks. - Each item: a concrete check with a clear pass condition (not a vague "verify X works"). - Right-size the list to the Targeted (changed + adjacent) depth so it fits the available window. - Flag recurring high-value items that should be promoted to automated regression tests. ## Deliverables 1. The ordered, prioritized regression checklist with pass conditions. 2. A short rationale linking each section to a change or risk. 3. Items recommended for automation and any coverage gaps. Keep it actionable and lean; ask only if genuinely blocked.