What is end-to-end testing?
The test that behaves like a customer. Here is where it fits beside the faster tests underneath it.
In short
End-to-end testing checks a complete user journey through the running application, the way a customer would: a script drives a real browser to sign up, create something, pay and see the result, touching the interface, the server, the database and outside services together. Tools such as Playwright and Cypress automate it.
Also called: E2E testing, E2E tests, Browser testing
Why it matters when your prototype goes to production
The journeys that make you money, sign-up, onboarding, checkout, are exactly the ones nobody re-tests by hand after every change, because they take too long. An end-to-end test does it in minutes on every release, and tells you the day a change breaks the path customers pay through.
| Test | What it checks | Speed | How many |
|---|---|---|---|
| Unit | One function on its own | Milliseconds | Many |
| Integration | Parts together, such as code and a real database | Seconds | Some |
| End-to-end | A whole journey in a browser | Seconds to minutes | A few, on key paths |
End-to-end tests are the slowest and most brittle kind, so keep them for the journeys that matter most, and cover the detail with faster tests underneath. Zulu, for instance, runs most of its test files against a real PostgreSQL engine rather than a mock.
Common questions
Is end-to-end testing the same as integration testing?
No. Integration tests check that some parts work together. End-to-end tests check the whole journey through the running app, usually in a browser.
Is Playwright an end-to-end testing tool?
Yes. Playwright drives real browsers and is widely used for end-to-end tests, as is Cypress.
Related terms
Sources
More on this: Production architecture & security · All glossary terms
Built something in Lovable you want people to rely on?
We are the engineers who take it the rest of the way — secured, tested, released and supported.