What is End-to-End Test?
Turkish: E2E Test
An end-to-end test validates a user journey across the UI, API, database, and integrations in a flow close to real usage.
What is an End-to-End Test?
An end-to-end test checks a critical user journey from start to finish. Instead of testing one function in isolation, it verifies the combined behavior of the interface, API, authentication, database, and sometimes third-party services.
How Does It Work?
An E2E tool controls a real browser or browser engine. It navigates like a user, fills forms, clicks buttons, and checks a visible result or backend state. Playwright, Cypress, and Selenium are common tools for this type of testing.
For example, an e-commerce flow such as “add product to cart, go to checkout, attempt payment with a test card, and see the order confirmation” is a good E2E candidate. Testing every small calculation rule this way creates a slow and brittle suite.
Difference from Unit Testing
A unit test verifies one function, class, or component in isolation. An E2E test is more expensive but shows whether the integrated system behaves correctly. For that reason, it should focus on a small number of high-value user journeys.
Business Use
Login, checkout, booking, application forms, invoice creation, and permission checks in admin panels can be protected with E2E tests. In test automation, stable selectors, test data setup, parallel execution, screenshots, and videos make failures easier to debug.
Related Terms
Integration testing verifies the expected data flow when multiple modules, services, or external systems work together.
PlaywrightPlaywright is an open-source browser automation tool for testing web user flows across Chromium, Firefox, and WebKit with repeatable scripts.
Test AutomationTest automation runs selected test scenarios repeatedly with tools and sends the results into CI pipelines or reporting systems.
Unit TestA unit test verifies a small code unit such as a function or class quickly and automatically while isolating external dependencies.