Create intermediate Works with: Any AI

Test Plan for a New Feature

Table output Has example

Create a risk-based manual and automated test plan.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Create a risk-based test plan. Feature description and acceptance criteria: [FEATURE_AND_CRITERIA]. System context and integrations: [SYSTEM_CONTEXT]. Users and devices: [USERS_AND_DEVICES]. Release date and team: [RELEASE_AND_TEAM].

Return as tables:
1. Risk analysis: Risk | Likelihood | Impact | Test focus. Include data loss, money, security, privacy, integrations, performance, and accessibility.
2. Test scenarios: ID | Scenario | Type (functional, negative, boundary, integration, usability, performance, security, accessibility) | Level (unit, integration, end-to-end, manual exploratory) | Priority | Automated? | Expected result.
3. Test data: Data needed | How created | Reset method.
4. Environments and configuration: what must be set up, including feature flags.
5. Exploratory testing charters (three, 60 minutes each) using the pattern "Explore X with Y to discover Z".
6. Entry and exit criteria: what must be true to start testing and to release, including defect thresholds.
7. Regression areas to re-check.
8. Rollout and monitoring: staged release, rollback conditions, and metrics to watch.

Provide the schedule and who tests what. Include the questions you would ask the product owner to clarify ambiguous acceptance criteria.

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.

Risk analysis (excerpt) for "saved payment cards"
Risk | Likelihood | Impact | Focus
Card data stored insecurely | Low | Critical | Security review, no raw numbers stored
Wrong card charged | Medium | High | Integration tests, manual checks
Scenarios
ID | Scenario | Type | Level | Priority
S1 | Add a valid card, pay with it | Functional | E2E | P1
S2 | Add an expired card | Negative | Integration | P1
S3 | Remove default card | Boundary | Integration | P2
Charter: Explore the checkout with saved cards using two browsers to discover session conflicts.
Exit: no open P1 defects; rollout to 5% then 50% then 100%.

• test-plan
• qa