Why Frontend Chaos?
Frontend apps are where users experience backend failures. A retry policy, skeleton state, disabled button, or WebSocket reconnect loop can be correct in code review and still fail when real browser APIs behave badly.
Chaos Maker lets product teams test those failure paths inside the same E2E suites that already protect happy paths.
What this catches
Section titled “What this catches”- Error states that never render because the app assumes JSON always parses.
- Retry buttons that issue duplicate writes.
- Loading states that block the user forever.
- WebSocket UIs that silently stop updating after a disconnect.
- Checkout and upload flows that have no abort recovery.
Why browser-side injection
Section titled “Why browser-side injection”Browser-side chaos needs no backend changes, shared test environment, or proxy infrastructure. It patches standard APIs in the test page and records every decision as a ChaosEvent, which keeps the blast radius small and the assertions close to the UI behavior.
What comes later
Section titled “What comes later”v0.3.0 focuses on framework reach, docs, and deterministic replay. Protocol-level and network-layer work is intentionally deferred to v0.4.0.