Verification · Testing
End-to-end browser tests
Drives a real browser through user flows to catch breakage across components, routing and the network.
Sub-techniques
-
Scripted flows
V1020.001Deterministic scripts for critical paths: sign-in, checkout, settings.
-
Agent-driven exploration
V1020.002An LLM agent drives the browser from a natural-language description of the flow.
How to build it
- Cover the few flows that would page someone if broken.
- Seed test data per run and use stable selectors (roles, test ids).
- Record traces and screenshots on failure as CI artifacts.
Signals in a repository
- playwright.config or cypress.config and an e2e/ directory.
- A CI job that starts the app and runs the browser suite.