← ClaudeAtlas

api-chaos-runnerlisted

Use when an existing API test suite should be rerun under network faults to prove retries, timeouts, circuit breakers and fallbacks work. Injects latency, timeouts, dropped connections, bandwidth caps and packet loss with Toxiproxy and reports which assertions break under which fault.
testland/qa-skills · ★ 0 · Testing & QA · score 72
Install: claude install-skill testland/qa-skills
# api-chaos-runner ## Overview Most API tests run against perfect networks: <1ms latency, no packet loss, infinite bandwidth, deterministic ordering. Real production isn't like that. **Network chaos testing** drives the existing tests under controlled network impairment - the team discovers which retry / circuit-breaker / timeout patterns actually hold up before real customers find out. The canonical open-source primitive is **Toxiproxy** - Shopify's "TCP proxy to simulate network and system conditions for chaos and resiliency testing" ([toxiproxy-readme][toxiproxy]). The pattern: sit Toxiproxy between client and upstream; manipulate **toxics** (latency, timeout, bandwidth, etc.) during test execution. [toxiproxy]: https://github.com/Shopify/toxiproxy This skill is **build-an-X** - the workflow chains the team's existing API tests (Postman / Karate / RestAssured / Tavern / Schemathesis) through a Toxiproxy-managed connection and orchestrates a per-scenario chaos matrix. ## When to use - The API has documented resilience requirements (retry on 5xx, circuit-break on 3 consecutive failures, timeout at 5s, etc.) and the team needs to **verify** them, not just document them. - A new external dependency just got added; the team wants to pressure-test fallback behavior. - An incident postmortem identified a "we should have caught this in testing" item; chaos coverage is the prevention mechanism for that class. - The team has integration tests already and wants to mu