Torture Test
Design long-form torture tests for high-load, malformed-input, timing, and resource-exhaustion scenarios. This complements fuzzing-in-ci: fuzzing finds inputs that crash; torture testing finds inputs that degrade, leak, starve, or recover incorrectly.
Scenario Types
- Endurance: repeated valid workloads over long duration with memory/FD/latency ceilings.
- Stress: high concurrency, burst input, large payloads, queue pressure.
- Adversarial input: slow-loris timing, malformed grammar sweeps, partial reads, truncation, retry storms.
Outputs
The skill emits scenario cards under .aiwg/test/torture/ and scheduled CI recipes under .aiwg/test/torture/ci/. PR-gating remains short; torture suites run nightly, hourly, or on demand.
Pass/Fail Criteria
Every scenario defines memory ceiling, file descriptor ceiling, latency tail, error recovery time, and acceptable error classes.
References
agentic/code/frameworks/security-engineering/skills/fuzzing-in-ci/SKILL.md.aiwg/security/curl-checklist-gap-analysis.md row 2, Practice 11
1---2namespace: aiwg3name: torture-test4platforms: [all]5description: Scaffold endurance, stress, and adversarial-input tests that reveal degradation rather than immediate crashes6requires:7 - target: parser, network service, allocator, CLI stdin handler, or other untrusted-input surface8ensures:9 - scenarios: endurance, stress, and adversarial-input scenario templates10 - ci-recipe: long-form nightly or scheduled test recipe distinct from PR-gating11errors:12 - no-target: no candidate surface detected and no explicit target supplied13invariants:14 - torture tests are long-form jobs, not unbounded PR blockers15 - pass/fail criteria include resource ceiling and recovery behavior16commandHint:17 argumentHint: "[--target <path-or-service>] [--type endurance|stress|adversarial|all] [--ci github|gitea|gitlab]"18 allowedTools: Read, Write, Bash, Grep19 model: haiku20 category: testing21 orchestration: false22 modelRole: efficiency23 modelTier: economy24---2526# Torture Test2728Design long-form torture tests for high-load, malformed-input, timing, and resource-exhaustion scenarios. This complements `fuzzing-in-ci`: fuzzing finds inputs that crash; torture testing finds inputs that degrade, leak, starve, or recover incorrectly.2930## Scenario Types3132- **Endurance**: repeated valid workloads over long duration with memory/FD/latency ceilings.33- **Stress**: high concurrency, burst input, large payloads, queue pressure.34- **Adversarial input**: slow-loris timing, malformed grammar sweeps, partial reads, truncation, retry storms.3536## Outputs3738The skill emits scenario cards under `.aiwg/test/torture/` and scheduled CI recipes under `.aiwg/test/torture/ci/`. PR-gating remains short; torture suites run nightly, hourly, or on demand.3940## Pass/Fail Criteria4142Every scenario defines memory ceiling, file descriptor ceiling, latency tail, error recovery time, and acceptable error classes.4344## References4546- `agentic/code/frameworks/security-engineering/skills/fuzzing-in-ci/SKILL.md`47- `.aiwg/security/curl-checklist-gap-analysis.md` row 2, Practice 11
jmagly 