Gain insights into writing automated tests for React apps with Jest and React Testing Library. Learn about simulating user interactions and testing asynchronous parts to enhance app reliability.

Testing React Apps with Jest and React Testing Library_468 x 60 copy 3.png

file.tar.gz

Jest - lesson 2

Jest with run command

Jest verbose

Jest coverage

Jest snapshot update

Jest react

Jest react-npm start

Jest react-copy

Jest react-C4

Jest react-C6

Jest react start c6

Jest - lesson 2-copy

Jest sandbox

Jest coverage-copy

Jest react-C4-start

Jest react-C4-start-5000

Jest react-npm start-5000

Jest react start c6-5000

Jest react-C8

The skills acquired from this course will allow you to write automated tests on your React app using Jest and React Testing Library, which are the de-facto testing tools for React. These tests will allow you to ship new versions of your app with confidence. The tests will also allow you to increase your release frequency, allowing you to get features to your customers quicker.

You will learn how to write robust tests that are resilient to breaking when code is improved and refactored, reducing maintenance costs.
The course will teach you how to simulate a user interacting with the app. Beyond that, it will also teach you how to robustly test asynchronous parts of the app.

Regular quizzes and exercises will reinforce knowledge throughout the course.

Testing React Apps with Jest and React Testing Library

## Understanding code coverage

Code coverage defines the amount of source code covered by tests. It allows us to identify gaps in our test suite quickly.

Jest gives us the following coverage statistics for each source file:

- **Statement coverage:** How many of the source code statements have been executed during test execution?

- **Branch coverage:** How many of the branches of conditional logic (for example,. branches in an `if` statement) have been executed during test execution?

- **Function coverage:** How many of the functions have been called during test execution?

- **Line coverage:** How many lines of source code have been executed during test execution?





# Understanding code coverage

Code coverage defines the amount of source code covered by tests. It allows us to identify gaps in our test suite quickly.

Jest gives us the following coverage statistics for each source file:

- **Statement coverage:** How many of the source code statements have been executed during test execution?

- **Branch coverage:** How many of the branches of conditional logic (for example,. branches in an `if` statement) have been executed during test execution?

- **Function coverage:** How many of the functions have been called during test execution?

- **Line coverage:** How many lines of source code have been executed during test execution?





Learn how to determine code coverage to identify missing tests from a test suite in this lesson.

Determining Code Coverage

Introduction

Getting Started with Jest

Using Matchers

Getting Started with React Testing Library

React Testing Library Queries

Firing Events

Mocking

Testing Different Types of Components

Appendix

Determining Code Coverage

Understanding code coverage