Delve into front-end testing principles, learn best practices for writing enduring tests, and discover strategies for E2E testing and integration into CI pipelines. Gain actionable testing insights.

React Testing 101 Component, Integration, and End-to-end Testing_1.png

tarball.tar.gz

jest

jest_describe

jest_onlytest

skiptest

aftereach

headless

foo2

opening

first_test

custom

final_job

foo_final

This course will provide you with important information, principles, and experience-based advice, to enter the world of testing methodologies. 

Here, you will learn the best practices to follow to write useful and lasting tests, how to test different user flows without a working back-end, how to write effective end-to-end tests (E2E), and how to integrate tests into development and Continuous Integration pipelines.

At the end of the course, you will be able to apply the fundamental principles of the test methodologies to understand what and how to test effectively.

Front-end Testing 101: Integration and End-to-end Testing

## Introduction 
When you run the test multiple times, you might encounter some errors like this:




As we can in the above illustration "_No articles are here_" string does not exist in the page.  The first screenshot is meant to show that the signup flow worked. So, why did the test fail?

Although [Cypress waits automatically](https://www.educative.io/courses/front-end-testing-integration/cypress-waitings-and-execution-order), it does not wait forever. `cy.get` and `cy.contains` wait up to 4 seconds (by default), but if the AJAX call lasts more than 4 seconds, the test fails.
## Solution

The fastest (but not the robust) solution is to increase the `cy.contains` timeout with the following change: 

```diff
-cy.contains("No articles are here").should("be.visible");
+cy.contains("No articles are here", { timeout: 10000 }).should("be.visible");
```

Now the test is going to succeed most of the time.


The complete test looks like the following:

> Note: You can see the Cypress UI better by opening the link next to **Your app can be found at:**

# Introduction 
When you run the test multiple times, you might encounter some errors like this:




As we can in the above illustration "_No articles are here_" string does not exist in the page.  The first screenshot is meant to show that the signup flow worked. So, why did the test fail?

Although [Cypress waits automatically](https://www.educative.io/courses/front-end-testing-integration/cypress-waitings-and-execution-order), it does not wait forever. `cy.get` and `cy.contains` wait up to 4 seconds (by default), but if the AJAX call lasts more than 4 seconds, the test fails.
# Solution

The fastest (but not the robust) solution is to increase the `cy.contains` timeout with the following change: 

```diff
-cy.contains("No articles are here").should("be.visible");
+cy.contains("No articles are here", { timeout: 10000 }).should("be.visible");
```

Now the test is going to succeed most of the time.


The complete test looks like the following:

> Note: You can see the Cypress UI better by opening the link next to **Your app can be found at:**

Learn to make the Cypress tests more stable.

Introduction

E2E Testing

The First E2E Test

Polishing the E2E test

Ajax Requests

Custom Commands

UI Integration Tests

Other Best Practices

Bonus Section

Conclusion

Appendix

Main E2E Test Defects: Stability

Introduction