Promtorium
Back to all prompts
TestingIntermediate

Regression Test Planner

Create a risk-based regression test plan from release scope, changes and impacted functionality.

Prompt
Act as a Senior QA Lead.

Create a risk-based regression test plan using:

Release scope and changes:
{{release_scope}}

Existing functionality:
{{existing_functionality}}

Known integrations and dependencies:
{{integrations_and_dependencies}}

Defect history or known risks:
{{defect_history_and_risks}}

Create:

1. Regression Objective
2. Change-Impact Analysis
3. Critical Business Journeys
4. Must-Test Areas
5. High-Risk Integrations
6. Data and Permission Scenarios
7. Positive, Negative and Boundary Coverage
8. Browser or Device Coverage, when relevant
9. Automation Candidates
10. Manual-Test Candidates
11. Test Prioritization
12. Entry Criteria
13. Exit Criteria
14. Test Environment and Data Needs
15. Defect Triage Rules
16. Residual Risk
17. Test Execution Sequence

Prioritize based on business impact, change likelihood, integration complexity and previous defects.

Do not recommend full regression by default. Identify what can be safely excluded and why.

Return a regression-scope table and execution checklist.

Replace the highlighted variables with information about your own product, feature or business objective before using the prompt.

{{release_scope}}{{existing_functionality}}{{integrations_and_dependencies}}{{defect_history_and_risks}}

Example in action

See how this prompt transforms a real input into a structured result.

Example input

Release scope: Redesigned mobile onboarding, email verification and new student eligibility check. Existing functionality: Standard subscriptions, account creation, login, payment and profile management. Integrations: Email provider, billing platform and external verification API. Known risks: Previous defects in expired email links and duplicate-account handling.

Example output

Highest-Priority Regression Areas: 1. Account creation and duplicate-account handling 2. Email-verification link validity and expiry 3. Billing-plan activation 4. Student-verification success, rejection and timeout 5. Existing standard-subscription purchase Critical Business Journey: Create account → verify email → verify student status → choose plan → pay → access service. Automation Candidates: - Valid account creation - Expired email link - Standard-plan purchase - API timeout handling Manual Candidates: - Mobile document-capture usability - Error-message clarity Exit Criteria: - All critical tests pass - No open severity-one or severity-two defects - Residual risks accepted by Product Owner

Tags

regressiontestingquality