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
Stubbing an AJAX request is easy and advantageous with Cypress because it allows us to concentrate on testing the front-end application instead of both the front-end and back-end. This is helpful because  E2E tests are often considered the only solution to front-end testing problems. But they come with so many disadvantages that they are often discouraged by many developers.

Two of the three main E2E testing problems are front-end developer independence and edge case replication. Both of these issues can be combated  easily with UI Integration Testing and back-end stubs. For instance, we can test the error paths that might happen in our registration flow. At the moment, our integration signup flow looks like the following:

## Signup flow


# Introduction
Stubbing an AJAX request is easy and advantageous with Cypress because it allows us to concentrate on testing the front-end application instead of both the front-end and back-end. This is helpful because  E2E tests are often considered the only solution to front-end testing problems. But they come with so many disadvantages that they are often discouraged by many developers.

Two of the three main E2E testing problems are front-end developer independence and edge case replication. Both of these issues can be combated  easily with UI Integration Testing and back-end stubs. For instance, we can test the error paths that might happen in our registration flow. At the moment, our integration signup flow looks like the following:

# Signup flow


Learn how to stub AJAX requests in Cypress to test the front-end application.

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

A Better Way to Front-end Test

Introduction

Signup flow