Quality Engineering API Performance Testing
Specify tool-neutral API load, stress, and recovery testing with parameterized workload...
Install
npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-api-performance-testing -g -a claude-code -y- Repository
- HoangNguyen0403/agent-skills-standard582
- Category
- Testing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,146 tokens
- Runs scripts
- No, instructions only
What it does
Specify tool-neutral API load, stress, and recovery testing with parameterized workload models, SLO percentiles, and finite overload bounds. Use when evaluating API latency, throughput, saturation, or recovery behavior under concurrent traffic.
API Performance, Load, and Recovery Testing
Priority: P1 (HIGH)
Workflow
- Parameterize Workload: Source arrival rate vs concurrency, request mix, duration, and SLO percentiles from approved requirements/SLOs. Missing approvals block execution, not offline planning.
- Preflight & Bound (C4): Verify explicit target authorization and synthetic isolation. Enforce distinct finite ceilings, each with its own unit,
maxArrivalRateRps,maxInFlightRequests/maxConcurrency,maxPayloadBytes, duration, plus cancellation hooks and continuous stop tripwires. A rate ceiling is not a concurrency bound. - Establish Phase-Specific Baseline: Exclude warmup. Measure baseline throughput, success latency, error latency ($p50, p95, p99$), and baseline error budget.
- Evaluate Overload & Degradation: Apply stepped ramp up to authorized stress cap. Distinguish expected shedding (e.g. 429/503) from unexpected system faults; abort if tripwires fire.
- Verify Post-Overload Recovery: Drop traffic to baseline/zero. In a dedicated post-stress window, verify return to baseline latency, error budget restabilization, and resource release against approved recovery SLO.
- Capture Evidence (C3): Emit complete C2 scenario and C3 evidence records; record unexecuted runs as BLOCKED/NOT RUN with explicit missing prerequisites.
