performance-report-analysis
Performance Report Analyzer
Interprets performance test results, identifies bottlenecks, classifies findings by severity, and produces two structured reports — one technical, one for business stakeholders. This skill starts where testing ends.
Scope boundary: This skill covers analysis and communication of results after
a test has run. For planning which tests to run, sizing VUs, or setting SLAs, use
performance-testing-strategy instead.
Output Format
After completing Steps 1–3, deliver two artifacts:
- Technical Report — for engineers and QA: raw findings, root cause analysis, severity classification, and concrete remediation steps.
- Business Report — for stakeholders: business impact framing, risk rating, and recommended decisions — no raw percentile numbers.
More from rcampos09/gatling-best-practices
gatling-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'.
12k6-best-practices
>
1locust-best-practices
>
1performance-testing-strategy
>
1