End-to-End Test

You might say

Like a real user, create an itinerary from the travel home page, save it, reopen it, and confirm the confirmation page shows that same trip.

An end-to-end test follows a complete system flow from a user's entry point to the final result.A browser can register, sign in, create a trip, and reach confirmation across pages, services, and data storage. This is evidence that the user journey works. Calling one API or checking one function is important but not end-to-end.

Know first

Integration Test

E2EE2E TestEnd-to-End Test

How one trip booking goes from browser to confirmation

trip.local/hangzhou

Choose
Pay
Confirm

WEEKEND PICK

Two slow days in Hangzhou

West Lake · Longjing · Art Museum

One browser operates from the user entry to a confirmation number across the real page, API, and data path.

What end-to-end evidence proves

Start at the user entry point: The test clicks, types, navigates, and reaches a final page, giving repeatable evidence for the real critical path. It fits registration, pre-payment confirmation, and content creation.

Keep journeys few and representative: Full journeys are slower and depend more on environments, so cover essential success and high-risk failure paths first. Unit and integration tests still locate detailed rules faster.

Quick checkChoose the best answer

Which best proves the end-to-end path “a user can complete a booking”?

In a browser, enter an itinerary, submit it, reopen the confirmation page, and verify it shows the saved itineraryCall the create-itinerary API directly and check its statusPass one date to a date-formatting function

You can say this to an AI Agent

Add an E2E test for a trip booking: fill and save an itinerary in a browser, then reopen the confirmation page and verify that itinerary remains. After it passes, tell me which pages it visited and the final result it saw.

Learn next

1Smoke Test→2Regression Test→