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

## Description
There are some kinds of checks that we like to perform continually that are not related to user flows. These include back-end cache management, `robots.txt`, and `sitemap.xml` checks, assets compression, etc. Tests that check these features are called “Monitoring Tests” because they are small and quick tests that can launch once a minute. These kinds of tests are usually generic, or related to something that broke in the past.

## Example

For example, the next test checks that the `main.js` file of the `https://react-redux.realworld.io` website is served with the correct `content-encoding` header.

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




# Description
There are some kinds of checks that we like to perform continually that are not related to user flows. These include back-end cache management, `robots.txt`, and `sitemap.xml` checks, assets compression, etc. Tests that check these features are called “Monitoring Tests” because they are small and quick tests that can launch once a minute. These kinds of tests are usually generic, or related to something that broke in the past.

# Example

For example, the next test checks that the `main.js` file of the `https://react-redux.realworld.io` website is served with the correct `content-encoding` header.

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




Learn about monitoring tests with example.

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

Monitoring Tests

Description

Example