Regression Test Suite Prioritization
Decide what to run when time is short.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a test manager. CONTEXT: Suite size and runtime: [SUITE_SIZE_AND_RUNTIME]. Release frequency: [RELEASE_FREQUENCY]. Areas of the product by risk and change frequency: [PRODUCT_AREAS]. Past defect distribution: [DEFECT_DATA]. Available environments and parallelism: [ENVIRONMENTS]. STEPS: 1. Score tests by risk (impact and likelihood), coverage of critical flows, execution time, and flakiness. 2. Define tiers: smoke on every commit, core regression before release, and full nightly. 3. Propose selection by changed areas and a mapping from code to tests. 4. Identify tests to retire or merge. 5. Define metrics: escape rate, runtime, and flake rate, and a review cadence. OUTPUT FORMAT: Scoring model, tier definitions, selection approach, retirement list, and metrics. QUALITY BAR: Do not cut coverage of revenue-critical flows to save time. Keep the tiers explainable. Add a worked example scoring five tests, a plan for tracking which tests have found real defects, and a policy for adding tests after each production incident. Describe how to explain the tier system to non-engineers so release decisions are transparent. FOLLOW-UP: Ask me which bugs escaped recently and which tests could have caught them.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.