End-to-end Test
An end-to-end (E2E) test follows a complete user or business journey through the assembled and deployed system.
Another example
A tester signs in with a test account, buys one product, and pays through a safe test payment service. The order must appear on the confirmation page and in order history. Calling the order function directly skips the end-to-end path.
Main parts
- 01user journey
- 02assembled system
- 03observable outcome
Use it when
Use this term for a few critical journeys that must work across the whole product.
Do not use it when
Do not test every possible case with slow E2E tests, and do not accept tests that fail at random.
Name used in code
browser → app → service → data → UI Before you ship
Check the environment and prepared test data (fixture). Define a result you can observe, failure and edge cases, isolation, stable inputs, useful error details, and cleanup. Set a time budget, owner, and flaky-test rule.
Outcome: Use End-to-end Test to gather repeatable evidence about this behavior or quality risk. User context: A tester signs in with a test account, buys one product, and pays through a safe test payment service. The order must appear on the confirmation page and in order history. Calling the order function directly skips the end-to-end path. Validation approach: End-to-end Test. Why it fits: Use this term for a few critical journeys that must work across the whole product. Do not use it when: Do not test every possible case with slow E2E tests, and do not accept tests that fail at random. Test requirements: Name the system and test environment. Define prepared test data, other inputs, and the result you can observe. Include failure and edge cases, allowed error, isolation, and cleanup. Test operations: Make failures easy to diagnose. Control random or changing inputs. Name an owner. Keep the test fast and simple enough for its release gate. Acceptance criteria: The test fails for the known bug and passes after the fix. It repeats in the target environment, gives useful evidence, and does not expose or change unrelated data. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Release gate, environment, prepared test data, allowed error, time budget, owner, and flaky-test rule.
Check this request
Review the current use of End-to-end Test. Definition: An end-to-end (E2E) test follows a complete user or business journey through the assembled and deployed system. Release checks: Check the environment and prepared test data (fixture). Define a result you can observe, failure and edge cases, isolation, stable inputs, useful error details, and cleanup. Set a time budget, owner, and flaky-test rule. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.