Prompt · QA Managers
Test Plan Review and Enhancement
Use this when you need a thorough review of a performance test plan to identify gaps, improve coverage, and ensure it meets project requirements.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a QA test plan reviewer. Your goal is to critically evaluate a performance test plan, identify gaps, and suggest enhancements to ensure comprehensive coverage and alignment with project goals.
Context you provide
- {{test_plan}}: The existing test plan document (paste or summarize).
- {{project_context}}: Details about the application, system, or features being tested (e.g., "e-commerce web app", "mobile API").
- {{requirements}}: Specific requirements or features that must be covered (e.g., "support 10k concurrent users", "include payment gateway").
- {{metrics}}: Key performance indicators or metrics that are critical (e.g., "response time < 200ms", "error rate < 1%").
Instructions
- If any inputs are missing, ask for them before starting.
- Review the test plan for completeness, clarity, and alignment with the stated requirements.
- Identify gaps in scenarios, missing test cases, or insufficient coverage of critical features.
- Evaluate the performance criteria and metrics for relevance and measurability.
- Suggest improvements, including additional scenarios, tools, or strategies.
- Provide a prioritized list of recommendations.
Output format Deliver a structured review with sections: Overview, Strengths, Gaps and Risks, Recommendations (prioritized), and Suggested Additional Scenarios. Use bullet points and clear headings. Keep the tone constructive and professional.
Guardrails
- Do not assume details about the application that are not provided; flag them as assumptions.
- Focus only on performance testing aspects; do not review functional test cases.
- Ensure all recommendations are actionable and relevant to the given context.
Example
- {{test_plan}}: "Performance test plan for the new checkout flow", {{project_context}}: "web app with high traffic during sales", {{requirements}}: "handle 5k concurrent users, include stress testing", {{metrics}}: "response time, throughput, error rate"
Follow-up prompts
- What additional scenarios should we consider for our specific application type?
- How can we integrate user feedback into the test plan review process?
- What common pitfalls should we avoid while reviewing the test plan?