ring:dev-chaos-testing

Chaos testing with Toxiproxy validates graceful degradation by injecting controlled faults like network latency and connection loss into external dependencies, verifying that Go and TypeScript projects handle infrastructure failures without crashing.

To set up chaos tests, dispatch a QA Analyst to configure Toxiproxy fault injection for the target unit, then run the five-phase Gate 7 workflow to simulate failure scenarios across all external dependencies in Go and TypeScript projects.

Yes, this chaos testing workflow supports auto-detection and validation of external dependencies. If dependencies are missing, the system automatically identifies them before applying Toxiproxy fault injection during the Gate 7 sequence.

The best way to validate network partition resilience is orchestrating a dual-gate workflow via Toxiproxy. It guides projects from normal operation through fault injection to recovery, producing standardized outputs for QA review and risk assessment.

No, it implements automated input validation for unit IDs, external dependencies, and language. The system validates these parameters automatically before proceeding with Toxiproxy chaos test setup and the structured five-phase workflow.

You need to run Gate 7 chaos testing when a task has external dependencies. It validates graceful degradation under failure by simulating infrastructure issues using Toxiproxy across Go and TypeScript projects before the next gate handoff.