performance-testing-strategy
Performance Testing Strategy Designer
Guides QA engineers through designing a complete, structured performance testing strategy by gathering context through targeted questions and applying industry best practices.
Important: Always gather context first (Step 1) before producing any output. Do not skip to recommendations without understanding the system and its constraints.
Output Format
After completing Step 1, deliver a strategy document with these sections:
- System Under Test (SUT) summary — what you understood about the application
- Recommended test sequence — which test types to run and in what order, with rationale
- Per-test definition — for each type: goal, user load, duration, ramp-up, success criteria
- Metrics to collect — response times, throughput, error rates, infrastructure metrics
- Risks and prerequisites — what must be in place before testing starts
Step 1 — Gather Context
More from rcampos09/performance-testing-skills
k6-best-practices
>
34gatling-best-practices
Guides developers and testers in writing, fixing, and structuring Gatling load test scenarios. Use this skill whenever the user mentions load testing, performance testing, stress testing, Gatling, virtual users, VUs, ramp-up, injection profiles, simulations, JMeter migration, k6 migration, throughput, response time SLAs, or wants to benchmark an API or service — even if they don't explicitly say 'Gatling' or 'performance test'.
25performance-report-analysis
>
13locust-best-practices
>
5