intermediate

E2E user flows

Cover the smallest set of critical journeys with controlled data, stable locators, network control, and failure artifacts.

E2E user flows cover critical journeys end-to-end: sign-up, purchase, invite teammate, export report. Keep the set small, data-controlled, and independent—seed via API, reset between runs, and tag smoke versus full regression.

Stable locators, network stubs only where external systems are unreliable, and artifacts (trace, video, HAR) on failure speed triage.

On interviews: prioritize three flows for a SaaS billing product and justify what you deliberately exclude from E2E.

Common pitfalls: testing every validation message in the browser, shared accounts causing collisions, and environment drift between local and CI.

The trade-off is highest user confidence versus slowest, flakiest suite—resist scope creep.

Checklist:

List critical journeys tied to revenue or compliance.
Isolate data and auth per test.
Capture debug artifacts on failure.