# End-to-End Testing

End-to-end testing exercises a complete product workflow across integrated parts to check an externally visible outcome.

- Type: practice
- Domain: Engineering & architecture
- Level: Intermediate
- Last reviewed: 2026-10-19
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/end-to-end-testing/>)

## What it means

End-to-end testing follows a workflow through the system boundary the team intends to verify, such as placing an order and seeing its confirmation. It often uses a browser but can start at an API. The environment and any simulated external services must be stated so the claimed coverage matches what actually ran.

## Why it matters

A journey can fail because of routing, authentication, wiring, or asynchronous processing even when individual components pass. A small set of complete-workflow checks helps detect these failures before a release reaches users.

## When to use it

Use it for critical journeys and integration risks that smaller tests cannot establish. Prefer focused checks for exhaustive business-rule combinations; browser-driven tests are expensive places to test every calculation. Do not treat automated completion as evidence of usability.

## How it works

1. Choose a small set of important workflows and define successful outcomes.
2. Provision isolated accounts and predictable data in a representative environment.
3. Perform user-visible actions using stable labels and resilient waiting conditions.
4. Verify the final business result rather than only a success message.
5. Capture useful failure evidence and remove flaky causes instead of masking them with retries.

## A practical example

A marketplace test signs in, reserves a sandbox listing, completes a simulated payment, and verifies the order appears in history. It catches a callback-routing error. The team records that the payment provider’s live processing is outside this test’s coverage.

## Where it breaks

Failures can be slow to diagnose and depend on many systems. Simulated services reduce instability but narrow coverage. Passing a few journeys cannot prove all states, browsers, accessibility needs, or production conditions are correct.

## Common mistakes

- Equating a mocked checkout response with a verified payment integration.
- Using fixed sleeps that fail under variable load.
- Expanding browser tests until feedback becomes too slow to act on.

## Sources

1. [Just Say No to More End-to-End Tests](<https://testing.googleblog.com/2015/04/just-say-no-to-more-end-to-end-tests.html>) — Google Testing Blog · Engineering guidance
2. [Best Practices](<https://playwright.dev/docs/best-practices>) — Playwright · Official documentation

## Related topics

- [Continuous Delivery](<https://wiki.soroush.uk/topic/continuous-delivery/>)
- [Acceptance Criteria](<https://wiki.soroush.uk/topic/acceptance-criteria/>)
- [Integration Testing](<https://wiki.soroush.uk/topic/integration-testing/>)
