Gain insights into testing React apps effectively. Learn about unit tests with Jest and automated integration tests using Selenium to ensure robust, customer-ready software.

Complete Guide to Testing React Apps with Jest and Selenium.jpg

jest.tar.gz

start_and_test

test

This course will teach you to properly test your React applications, starting from basic unit tests with Jest to automated integration tests using Selenium. You will learn everything from the ground up to the most advanced concepts that will give you confidence in shipping your software to customers.

Complete Guide to Testing React Apps with Jest and Selenium

# Automocking
You noticed that, to mock a module, we had to write:
```javascript
jest.mock('module name');
```
However, there is one more approach that makes even this line unnecessary.
> Note: I show you this approach merely for informative purposes, but I myself have never found it useful in production projects due to its nature. If you do end up using it somewhere, do let me know about your experiences in the course discussion!

If you open the file `setupTests.js` and add this line to it:
```javascript
jest.enableAutomock();
```
You will enable _automocking_ across all test code. What is automocking and how is it different from `jest.mock`?

Automocking mocks _every single_ import in testing code and replaces it with either a `jest.fn()` or a specified mock from `__mocks__` folder. To actually test something, you would have to __unmock__ a module so you can actually access that code:
```javascript
import MyComponent from './MyComponent';

// MyComponent is currently mocked
// To test it, you need to add
jest.unmock('./MyComponent');

// now you can test it
```

The upside of this approach is its simplicity and safety. You do not have to worry about mocking API functions because __all__ functions are already mocked.

The downside of this approach is un-mocking everything you want to test and configuring the mocks you decide to leave mocked. While mocking is essential, clean coding practices should keep such unbreakable dependencies to a _minimum_. If you start relying on mocks so much that automocking becomes viable, there may be a bigger problem in your code.

In this (very short) optional lesson, learn  one more way to mock modules in your code.

Introduction

Introductory Quiz

Write Your First Tests

Basic Testing Exercises

More Tests

Mocking Modules in Unit Tests

Mocking Exercises

More on Integration Tests

Bonus: Custom Matchers

Automocking

Automocking