end-to-end test
A test that drives the whole system from the outside, often through a browser or public API, with every part running.
In more detail
End-to-end tests give the most realistic confidence but are the slowest, the most expensive to set up and the most likely to fail for reasons unrelated to your change. Keep a handful for the most important journeys and run them on a schedule or before a release rather than on every save.
Examples
e2e 1 tests passedA Playwright test that fills the checkout form and asserts the confirmation appears.Related terms
- unit test — An automated check of one small piece of code, such as a single function, that runs quickly and on its own.
- integration test — A test that checks several real parts working together, such as the service talking to a real database.
- test pyramid — A guide for balancing a test suite: many fast unit tests, fewer integration tests and a small number of end-to-end tests.
- user journey — The sequence of steps a user takes to get something done with a service, such as searching and checking out.
- Playwright — Microsoft's open-source tool for automating Chromium, Firefox and WebKit browsers, widely used for end-to-end and visual tests.
- flaky test — A test that sometimes passes and sometimes fails on the same code, because it depends on something it does not control.
- ice cream cone — An upside-down test pyramid, with most tests slow and end-to-end and few unit tests, usually reached by accident.
Taught in
- Continuous Integration — DevOps & Site Reliability Engineering
- Testing Strategies And The Test Pyramid — DevOps & Site Reliability Engineering
- End-to-End Testing with Playwright: Multi-Tier Suites — Production Full-Stack Engineering
- Full-Stack System Verification: Capstone Integration — Production Full-Stack Engineering
- The Test Pyramid And Where It Is Wrong — Automated Testing, TDD & Quality Engineering