Search⌘ K
AI Features
Home
Courses
Front-end Testing 101: Integration and End-to-end Testing

Main E2E Test Defects: Utility in Case of Failure

Explore common defects in main end-to-end tests, focusing on their utility when tests fail. Understand how to interpret test feedback, distinguish between implementation errors and user-facing issues, and apply effective debugging strategies to maintain reliable front-end user flows.

We'll cover the following...

Utility in case of failure

A written test is useless when it fails. There are many reasons that could cause the signup flow to fail. Some of these include:

  1. The host does not work.
  2. The page does not respond.
  3. One of the input fields is not rendered.
  4. The button is not rendered.
  5. The button does not trigger the correct Redux action.
  6. The AJAX call does not start.
  7. The AJAX call has the wrong request payload.
  8. The API does not work and it does not respond.
  9. The API returns the wrong payload.
  10. The functions that manage the authentication do not perform the expected job.
  11. The user already exists.
  12. Everything is managed correctly but the redirect to the home page does not work.
  13. The home page does not show the “No articles are here” text.
  14. The home page shows a slightly different message to the user (ex: “Click on ‘New Post’ to add your first contribution”).

Implementation details errors

Some of the possible errors that can occur at the beginning of the test include:

  1. The button does not trigger the correct Redux action.

  2. The functions that manage the authentication do not do the expected job.

These errors fall under. “implementation details”. We are testing the whole front-end application ...