Skip to main content
Frontend Glossary

Frontend engineering · Code quality

End-to-End Test

Also called: E2E, Browser test, End to end testing

Drive a real or headless browser like a user—clicking and navigating—to verify a whole path works, not just one function.

In detail

E2E starts from the user: open a page, fill a form, wait on requests, assert the result. It catches routing, auth, and "button hidden by CSS" issues unit tests miss—and it's slower and flakier to maintain.

Keep a small critical set: login, checkout, publish. Leave fine edges to unit tests. When AI writes E2E, pin fixtures and prefer role/label selectors over brittle class names.

Complements dogfooding: automation regresses known paths; exploratory UX still needs humans.

Developer info
Term ID
eng-e2e-test
DOM selectors
No DOM cues. This concept isn't detected directly on a page.
Priority
1 · when several match at the same level, the higher priority wins
Version
v1 · updated Oct 5, 2026