End-To-End Testing

What is E2E testing?

End-to-end (E2E) testing, also known as UI testing, tests system workflows from the end user’s perspective. We test all the system components to see if they are working correctly. The primary aim of E2E testing is to ensure that the entire system is functioning correctly. Typically, testers who are familiar with the system write E2E tests. E2E tests generally are slower than unit and API tests because they test the entire system. They are also more prone to flakiness. Flaky tests randomly fail even though there was no code change.

In a real-life situation, let’s say we want to test the E2E workflow of completing a feedback form for a health-care application. The user would navigate to the home page, click the link to the feedback page, fill out the form, and submit it. After submitting the form, they should see a message thanking them for their feedback. We can view the workflow in the browser.

Execute the application below and click the provided Educative URL to view it in a browser.