What Is End-to-End (E2E) Testing?

End-to-end testing verifies an entire application flow works correctly from the user's perspective, typically by driving a real browser through real user int...

Published November 15, 2026

End-to-end (E2E) testing drives the whole application the way a real user does, in a real browser against a running system, to verify complete workflows such as sign-up or checkout.

The concept

E2E tests cover the full stack: UI, API, database and third-party integrations. They give the most confidence but are slower and more brittle than unit tests.

Tools: Playwright, Cypress and Selenium. Keep them few and focused on critical user journeys.

What it exercises

clicksqueriesBrowsertest scriptApp + APIreal serverDatabasetest data
One test touches every layer.

Practical examples

Playwright test

import { test, expect } from '@playwright/test'
test('user can log in', async ({ page }) => {
  await page.goto('/login')
  await page.fill('#email', 'a@x.com')
  await page.fill('#password', 'secret')
  await page.click('button[type=submit]')
  await expect(page).toHaveURL('/dashboard')
})

Run

npx playwright test

Stable selectors

<button data-testid="checkout">Pay</button>

Common mistakes

  • Too many E2E tests, making CI slow.
  • Brittle selectors based on CSS classes.
  • Shared test data that makes tests depend on each other.

Key takeaways

  • Tests whole user journeys.
  • Slow but high confidence.
  • Few, focused, stable selectors.

FAQ

E2E vs integration?

Integration tests combine some components; E2E tests the full system.

How do I reduce flakiness?

Use auto-waiting tools, isolated data and test ids.

More General articles