QA Foundations
End-to-end testing
Also known as: E2E testing
End-to-end testing exercises a complete user journey through a running system — browser or app, real services, real database — verifying that the integrated whole behaves correctly rather than any single component.
E2E tests catch the class of defect nothing else does: the failures that live in the seams between components that each work correctly alone. That is why they are worth having and why removing them entirely is a mistake.
They are also the slowest and least reliable layer by a wide margin, because every dependency is a chance to be non-deterministic — network timing, animation, data state, a third-party service. Google measured 14% flakiness in its large tests against 0.5% in small ones. The standard guidance is to keep E2E coverage for critical paths and push everything else down the pyramid.
- Catches defects that live between components, which unit tests cannot see.
- Slowest and flakiest layer — roughly 14% flaky against 0.5% for small tests in Google data.
- Reserve for critical paths; an E2E-heavy suite is slow by construction.
Related terms
See it in your own test results
Qualflare detects flaky tests, clusters failures by root cause, and scores release risk from the test results you already produce in CI. Start free.
Start free with Qualflare← Back to the testing & observability glossary.
Last reviewed September 9, 2026