End-to-End Testing

Site Admin · 11 Sep 2026 · 7 views

End-to-End Testing

Through the User's Eyes

End-to-end (E2E) tests drive the full running application exactly as a user would: opening a browser, clicking buttons, filling forms, and verifying the result. They are the only automated tests that prove the deployed system works, from the front end through every layer to the database.

The Tools

Modern E2E tools such as Selenium, Cypress, and Playwright bundle a browser, a driver, and a rich API. Selectors are the key idea: tools find elements by CSS selectors or by roles and accessibility attributes, then click and type into them.

// Playwright example
await page.goto("https://app.example.com/login");
await page.fill("#email", "ada@example.com");
await page.fill("#password", "correct-horse");
await page.click("button[type=submit]");
await expect(page).toHaveURL(/dashboard/);

In that spec, page.goto opens the site, fill types into fields, click submits, and toHaveURL asserts the outcome.

Choosing Journeys

E2E tests are expensive, so pick the journeys that matter most: authentication, checkout, account creation, and anything that makes or loses money. Cover the happy path plus one or two critical failure paths. Do not try to cover every form field at this level; that detail belongs to lower levels of the pyramid.

Keeping Them Stable

E2E tests earn a reputation for flakiness when they are written carelessly. Defense in depth:

Prefer accessible selectors (roles, labels) over brittle CSS class names.
Wait for elements explicitly rather than adding fixed sleeps.
Reset the database before each test for a known starting state.
Run them against a stable test environment, not a moving production.

Value and Cost

An E2E suite that protects the main journeys gives enormous confidence: if it is green, the product works for a real user. Keep the count low, keep the journeys critical, and treat flaky tests as defects to fix rather than ignoring them.