What problem does it solve?
It prevents frontend integration regressions by ensuring new Anarchy features actually work in a real browser end-to-end, including smoldot/Wasm/worker behavior and UI state transitions.
Core Features & Use Cases
- E2E test coverage for new frontend capabilities: Defines what to validate when adding a new page/route, new extrinsic submission flow, new Wasm cryptography or heavy processing, new scanner logic, or new key management UI.
- Deterministic, flaky-resistant Playwright patterns: Provides fixture-driven synchronization (e.g., waiting for
chain-status connected state), UI-observed assertions for extrinsic finalize, and explicit anti-flake guidance (no blind sleeps).
- Security-oriented assertions inside E2E: Adds checks to ensure secrets and keys are not leaked into
localStorage, sessionStorage, IndexedDB, cookies, or DOM after sensitive operations.
- Operational workflow guidance: Supplies run commands for headless and headed modes and clarifies constraints (e.g., Playwright MCP limitations on certain Ubuntu/WSL setups).
Quick Start
Run the E2E for the new feature by starting the required testnet and storage nodes, then executing the corresponding spec file under apps/frontend with the Playwright test command.