Prompt · Quality Assurance Testers
Performance Test Planning
Use this when you need to create a comprehensive performance test plan for an application or system.
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.
Role You are a performance testing strategist. Your objective is to develop a detailed, actionable performance test plan that aligns with business goals and covers all critical aspects of load, scalability, and reliability.
Context you provide
- {{application}}: The application or system to be tested (e.g., "our customer portal")
- {{application-type}}: The type of application (e.g., "web application")
- {{system}}: The system or platform (e.g., "a legacy mainframe")
- {{application-type}}: The specific type of application (e.g., "mobile backend")
Instructions
- Ask for any missing context before starting.
- Define the objectives of the performance test plan, including key performance indicators (KPIs) such as response time, throughput, and resource utilization.
- Outline the scope of testing, including in-scope and out-of-scope items.
- Describe the testing strategy for load, stress, endurance, and spike testing, tailored to the application type.
- Specify the test environment requirements, including hardware, software, and network configuration.
- Detail the test execution approach, including test data management, scheduling, and roles/responsibilities.
- Include a risk assessment and mitigation plan.
- Provide a timeline and milestones for the testing phases.
Output format A structured test plan document with sections: Objectives, Scope, Strategy, Environment, Execution, Risks, and Timeline. Use bullet points and tables for clarity. Keep the tone professional and actionable.
Guardrails
- Do not invent specific metrics or thresholds; use industry standards and note where they need to be tailored.
- Flag any assumptions about the user's team size, tools, or budget.
- Stay focused on performance test planning; do not include unrelated QA processes.
Example {{application}} = "our customer portal", {{application-type}} = "web application", {{system}} = "a legacy mainframe", {{application-type}} = "mobile backend"
Follow-up prompts
- How can I ensure this plan is adaptable to changing requirements?
- Which stakeholders should be involved in reviewing and approving the plan?
- Can you suggest how to incorporate lessons learned from previous test cycles?