End-to-End Testing (E2E)
Testing that validates an entire application workflow from start to finish, simulating real user behavior across all integrated system components.
End-to-end tests exercise the full technology stack: the browser or client, the web server, APIs, databases, third-party integrations, and everything in between. They are the most realistic form of automated testing because they interact with the application the same way a user would.
E2E tests are typically the slowest and most brittle tests in a suite, so teams generally keep the number of E2E tests small and focused on critical user journeys. Popular E2E frameworks for web applications include Cypress, Playwright, and Selenium.
Why It Matters for QA Teams
Websites depend on many interconnected services. E2E tests confirm that the entire chain works together, catching integration failures that unit and component tests cannot detect.
Example
An E2E test for an online store: open the homepage, search for 'wireless headphones,' add the first result to the cart, proceed to checkout, fill in shipping and payment details, submit the order, and verify the confirmation page displays an order number. The test touches the search API, inventory service, payment gateway, and email service.