Introduction to Modernizing an Enterprise React App

Video Course Overview - Modernizing an Enterprise React App

Get familiar with the sample React application's folder structure and current functionality.

What We'll Build In This React Course - Hardware Handler

Introduction

Module 1 Introduction

Learn about the motivation behind React Hooks, the benefits it can bring, and the rules that apply to all Hooks in a React application.

React Hooks - Understanding The Basic Rules and Benefits

The useState Hook is the most similar to traditional state in React class-based components, and we'll look at examples of how it works to keep track of state in functional components.

React's useState Hook - Track Functional Component States

useEffect is a game-changing hook: originally compared to lifecycle methods in React components, it's close but not truly a direct comparison.

How Does React's useEffect Hook Work?

While less often discussed, the useRef Hook deserves covering because a time will come when it's the right solution to reach for; here, we'll talk about how useRef's "mutable" value property can be useful.

Learning About The React useRef Hook And Mutable Values

Context is a powerful API to pass state within React applications, and with the introduction of the useContext Hook, accessing state in any component (class or functional) is possible.

A Step-by-Step Guide to Using React's useContext Hook

Custom hooks are arguably the most important addition of all the hooks released with React 16.8.0. Explore how custom hooks can dramatically simplify sharing code between components.

An Introduction To Custom Hooks In React

This lesson is a summary of the React Hooks we've covered in Module 1.0

Module 1 Summary

React Hooks

Introduction to Module 2: Upgrading React App Version

Module 2 Introduction

Before we can do anything else, we must upgrade our sample app's React version to start taking advantage of the advances.

Upgrade the React app version

Avoid one of the most common developer woes: different devs coding with different environment versions with the help of Volta and Node Engines.

Dev Teams, Lock Down Environment Versions With Volta

This lesson is a summary of module 2.0, where we upgraded our React version and locked in our project configuration.

Module 2 Summary

Upgrade the React App

Introduction to module 3: Code formatting setup

Module 3 Introduction

Code formatting, especially when it's set up, so you don't even have to think about it, is the best.

Code Formatting - An Overview Of Prettier And How To Set It Up

Make JavaScript code quality better and avoid bugs with the help of a linter and a strict set of rules.

How To Set Up ESLint For Modernizing A React App

This lesson is a summary of the automated code formatting and linting we set up with the help Prettier and ESLint in Module 3.0.

Module 3 Summary

Configure Prettier and ESLint

Introduction to Module 4: Refactoring to hooks

Module 4 Introduction

We dip our toes into converting a class component to a functional one with Hardware Handler's home page.

Refactor Home.js

We get our first real taste of adding hooks while refactoring the App component.

Refactor App.js

The checkout page uses multiple API calls to correctly display the items a product manager wants to ship to stores.

Refactor Checkout.js

Ah forms, a painful Achilles heel of most web applications (React apps included) since the beginning of time.

Refactor ProductForm.js

We saved the best (i.e. the most complicated) component for last. The product list, with its filters and products, is no match for our newly honed skills though.

Refactor ProductList.js

This lesson is a summary of Module 4.0, where we systematically refactored our app's outdated class components to now use React Hooks.

Module 4 Summary

Refactor React Classes to React Hooks

Module 5 Introduction

We'll write our first custom hook to fetch department info for our application in one centralized place.

Our First Custom Hook: useDepartments

Custom hooks are good for more than just drying up duplicated code; they also help simplify our components.

Simplify Complex Components with the useProducts Hook

Some custom hooks can help simplify code beyond the original components they touch.

The useCheckout Hook will do Double Duty in our App

This lesson is a summary of module 5.0's custom hooks we added to Hardware Handler.

Module 5 Summary

Create Custom Hooks for the App

Introduction to module 6: The useContext Hook

Module 6 Introduction

Bring the Context API into Hardware Handler to decrease our reliance on props.

Simplify React Prop Management With A Context Hook

Context doesn't necessarily need to live at the top level of a component to be useful.

Setting Up Contexts To Share Functions Within A React App

This lesson summarizes our addition of the Context API and useContext Hooks in Module 6.0.

Module 6 Summary

Incorporate the Context API

Module 7 Introduction

This library took aim at a few fundamental flaws in the traditional way of integration testing JavaScript applications and really changed the game when it comes to automated testing.

Introducing React Testing Library And Its Automation Capabilities

We've got a little setup work to do before we get to the actual business of writing our tests.

Strategies For Simplifying Integration Testing For React Apps

React Testing Library's approach to integration testing like a user would interact with the DOM works very well with React's function-based components.

How To Write Tests For React Container Components

Test Hardware Handler's custom hooks

Not all of our testing for our React app relies so heavily on RTL — some files Jest can handle on its own.

A Guide To API Service Layer Testing With The Jest Framework

This lesson is a summary of module 7.0, where we started adding unit and integration tests to our app to increase our confidence our app works as expected.

Module 7 Summary

Integration Testing with Jest and React Testing Library

Module 8 Introduction

End-to-end testing has never been the easiest thing to do, but Cypress challenges that statement in a big way.

Cypress.io And End-To-End Testing - What You Need To Know

Cypress gives us a big helping hand organizing and getting started with our own e2es.

Add Cypress To A React App For Automated End-To-End Testing

Cypress makes the process of writing e2es relatively simple with lots of built-in methods and documentation to show you the way to use it effectively.

Write And Run End-To-End Test Flows With Cypress.io

The Studio feature makes e2e test writing faster and easier than it's ever been before.

Try out Cypress Studio

This lesson is a summary of module 8.0, where we integrated Cypress into a React app and wrote automated end-to-end tests.

Module 8 Summary

End-to-End Testing with Cypress

Introduction to module 9: Design system libraries

Module 9 Introduction

Design systems provide more than just a bunch of prebuilt components for developers.

Why use a Design System?

Setting Ant Design up takes a little doing because it's so customizable.

How To Add Ant Design System To A React App

Ant Design's thorough documentation makes the process of replacing custom components less difficult than it might otherwise be.

Swap out Some Simple Components

While these components require a little more effort to get working, the improvements they provide are worth the time.

How To Add An Ant Design System Form To A React App

This lesson summarizes module 9.0, where we learned about the benefits of a design system and incorporated the popular Ant Design into our own app.

Module 9 Summary

Bonus Module: Add a Design System Library

Recapping Modernizing an Enterprise React App

Summing It All Up

In this course we'll dive into all the ways to modernize an existing React application - from tooling and linting, to testing and Hooks. React is a powerful, extremely popular JavaScript framework, but keeping applications up to date with all that it has to offer is tough - especially when dealing with the larger, enterprise-level business applications many developers are responsible for.

## Why this course

The newline Guide to Modernizing an Enterprise React application will cover everything you need to know to confidently work on a React application of any size, in any state, and leave it better than when you found it. 

While many React tutorials start with the latest version of React, or gloss over all the other things required to make sure apps vital to a company's success keep running, this course does not. In 54 lessons spanning 10 modules, it tackles head-on, the many things that must be considered when building and maintaining large, complex React apps.

## Course modules 

As you progress through this course, you'll gain a deeper understanding for how and why React Hooks came to be, the importance of various types of automated testing and project configuration, and how to leverage design systems to improve your application. You will gain a detailed understanding of how to modernize a React app in a real-world scenario, bringing it in line with today's development standards. 

![Home page of the Hardware Handler sample React application](https://d2uusema5elisf.cloudfront.net/courses/newline-guide-to-modernizing-an-enterprise-react-app/module_10/lesson_00.00/public/assets/hardware-handler-home-page.png)

### Part one: tooling and setup

The first part of this course will consist of getting familiar with our example application, and doing the behind-the-scenes work to set it up for success. 

We'll learn about why React Hooks came about and how to use them, how to upgrade an outdated React app successfully, and how to use tools like Volta, ESLint and Prettier to improve the app's code and development experience.

- Module 0: Meet Hardware Handler - our outdated, but promising React application.
- Module 1: [React Hooks](https://reactjs.org/docs/hooks-intro.html#motivation) - why they were created, the issues they solve and how the most common ones work.
- Module 2: Upgrading a React app - our app needs an upgrade to use Hooks, and we'll streamline development with [Volta](https://volta.sh/).
- Module 3: Project configuration - adding [Prettier](https://prettier.io/) and [ESLint](https://eslint.org/) to our app will dramatically improve code quality.  

### Part two: refactoring the code

With our app configured for success, we'll get down to the business of refactoring Hardware Handler. 

I'll show you my strategy for converting class components to functional ones, and we'll go file-by-file keeping the app's functionality intact while upgrading it to use hooks - including custom hooks, and the Context API. 

- Module 4: Classes to functions - we'll take every class component and turn it into a functional component.
- Module 5: [Custom hooks](https://reactjs.org/docs/hooks-custom.html) - we'll identify where custom hooks can simplify our functional components further.
- Module 6: [Context API](https://reactjs.org/docs/context.html) - a few strategically placed React contexts will round out our code improvements.

### Part three: testing

An updated application is only half the battle for enterprise-level apps; development teams must also be confident in their continued success as the apps expand in size and scope. 

We'll add automated testing to our app using the widely accepted testing frameworks React Testing Library and Cypress.

- Module 7: Integration testing - the popular combination of [Jest](https://jestjs.io/) and [React Testing Library](https://testing-library.com/docs/react-testing-library/intro/) will be used to unit test smaller pieces of our app.
- Module 8: End-to-end testing - the ease of writing e2es with [Cypress Studio](https://www.cypress.io/) will blow you away.

### Bonus: design systems

Finally, I've included a special bonus module about how to incorporate design systems into an already existing application, and switch out components in a systematic way. Design systems and component libraries are quickly gaining ground - especially in big orgs with lots of apps and development teams. 

Being able to effectively use one is an important skill to learn.

- Module 9: [Ant Design](https://ant.design/) - we'll swap in the robust design system's components to handle our app's more complex interactions for us.

![Product page of the Hardware Handler sample React application](https://d2uusema5elisf.cloudfront.net/courses/newline-guide-to-modernizing-an-enterprise-react-app/module_10/lesson_00.00/public/assets/hardware-handler-product-page.png)

## Bottom Line

In 10 modules, we'll go step-by-step taking an app from outdated in every way to up to today's high standards, giving you ample practice and hands-on examples along the way. 

If you've been wanting to get more confident in your React skills _and_ see what it takes to build enterprise apps in today's world, this is the course for you.

![Checkout page of the Hardware Handler sample React application](https://d2uusema5elisf.cloudfront.net/courses/newline-guide-to-modernizing-an-enterprise-react-app/module_10/lesson_00.00/public/assets/hardware-handler-check-out.png)

In this course, you'll learn all the pieces that go into modernizing an existing React application so it can take advantage of the latest framework features and run well for years to come.

The newline Guide to Modernizing an Enterprise React App

How to modernize an existing React application according to today's standards

How React Hooks work compared to class components

How config tools Volta and Node engines simplify development

How to set up ESLint and Prettier to improve code quality

How to upgrade an existing React app and refactor the app as you go

How to write integration tests with React Testing Library to ensure app functionality

How end-to-end tests with Cypress can test mission critical user flows

How to incorporate a component library to speed up design and development time

Set up automated end-to-end testing in Hardware Handler

Like I was saying in the previous lesson, Cypress is really light years ahead of all the other end-to-end testing frameworks out there. And this even applies to its setup and integration into existing projects as well.

This lesson will focus on adding Cypress.io to our React application and configuring it to run tests — both in headless and headed mode, depending on the need.

 we begin our end-to-end testing? You can download it 

We'll need to add Cypress as a dev dependency to Hardware Handler before we can start to take advantage of its capabilities.

So, open up a new terminal instance and run the following command to 

The first time you install it, it will take a minute. There's a lot of good info, demos, and configuration that come along with the Cypress install, so be patient.

When it's done successfully, you'll see the new 

  "devDependencies": {
    "@testing-library/jest-dom": "^5.11.6",
    "@testing-library/react": "^11.2.2",
    "@testing-library/react-hooks": "^7.0.0",
    "@testing-library/user-event": "^12.2.2",
    "axios-mock-adapter": "^1.19.0",
    "babel-eslint": "10.1.0",
    "cypress": "^8.0.0",
    "eslint": "^7.24.0",

After the initial install is done, we'll make sure it worked.

If everything goes according to plan, your terminal should recognize that this is the first time Cypress is fired up.

And after the welcome message, a new window containing the Cypress Test Runner should automatically open up and look something like this.

A nice, new inclusion in addition to the Cypress Test Runner itself is a whole suite of predefined tests showing how to do various different types of tests with Cypress.

This wasn't available when I first started using Cypress, but luckily, the documentation and examples have been good since the start.

But if you were ever wondering how to do something and wanted a quick reference in actual tests you can modify, these samples are pretty helpful.

If you'd like to see the test runner in action, go ahead and click the 

 button. This will kick off all the preconfigured tests and give you a taste of how Cypress operates.

A little later in this lesson, we'll go over all the various pieces of code that go into making these tests work and how they're organized.

With Cypress installed in our project, it's time to add a few scripts to our 

 to make it easier to run Cypress in a browser that's visible to us for active development and debugging and to run Cypress in "headless" mode — the same way it would run for in a CI build pipelines.

 file, add the following two commands to our 

    "lint:fix": "eslint src/ --fix",
    "cypress:open": "cypress open",
    "cypress:run": "cypress run"
  },

 does just what we did manually from the command line a section ago: it opens the Cypress test runner browser so that we can interact with our tests.

In addition to being able to debug and test code in the browser, this test runner lets us be very targeted and specific about which test suites we want to run.

For instance, if you're only adding tests to one particular suite (or know that the code you changed should only impact the functionality for one set of tests), you can select only those tests to run in the interactive test runner instead of waiting for them all to run (which is what happens by default in headless mode).

This script runs Cypress in headless mode. When it begins, all the tests will run, but we won't see anything on-screen besides what's being printed out in the terminal.

This is the command that would be run if we had it set up as a build step in a continuous integration (CI) pipeline.

Typically, there should be very little difference between a run in the visible test runner and a headless run here, but for debugging purposes, it's useful to have both commands within easy access.

If you'd like, we can test out our new scripts now.

 folder in the terminal, run the following command:

At this point, the test runner should open in a new browser window.

Go ahead and close this down. And in the terminal, once again, issue our other command:

---
title: 'Add Cypress To A React App For Automated End-To-End Testing'
role: 'LESSON'
description: Cypress gives us a big helping hand organizing and getting started with our own e2es.
privateVideoUrl: https://fullstack.wistia.com/medias/akhw9b2azm
isPublicLesson: false
code: https://gitlab.com/fullstackio/books/newline-course-apps/paige-niedringhaus-modernizing-an-enterprise-react-app-app/-/tree/main/code/module_09/lesson_09.02/protected/source_code/hardware-handler-8-begin?ref_type=heads
---

# Set up automated end-to-end testing in Hardware Handler

Like I was saying in the previous lesson, Cypress is really light years ahead of all the other end-to-end testing frameworks out there. And this even applies to its setup and integration into existing projects as well.

**This lesson will focus on adding Cypress.io to our React application and configuring it to run tests — both in headless and headed mode, depending on the need.**

I> **Sample code zip file**
I>
I> Need a fresh copy of the sample app _before_ we begin our end-to-end testing? You can download it **[here](http://localhost:3001/assets/protected/courses/newline-guide-to-modernizing-an-enterprise-react-app/module_09/lesson_09.02/protected/source_code/hardware-handler-8.zip)**.

### Install Cypress in our app

We'll need to add Cypress as a dev dependency to Hardware Handler before we can start to take advantage of its capabilities.

So, open up a new terminal instance and run the following command to [install Cypress](https://docs.cypress.io/guides/getting-started/installing-cypress#Installing).

```shell
cd client/ && yarn add cypress --dev
```

The first time you install it, it will take a minute. There's a lot of good info, demos, and configuration that come along with the Cypress install, so be patient.

When it's done successfully, you'll see the new `"cypress"` library in your `package.json`.

```json { actualFilename=./protected/source_code/hardware-handler-8-ending/client/package.json endLine=60 startLine=52 statedFilename=client/package.json url=https&#x3A;//gitlab.com/fullstackio/books/newline-guide-to-modernizing-an-enterprise-react-app/module_09/lesson_09.02/protected/source_code/hardware-handler-8-ending/client/package.json#L52 }
  "devDependencies": {
    "@testing-library/jest-dom": "^5.11.6",
    "@testing-library/react": "^11.2.2",
    "@testing-library/react-hooks": "^7.0.0",
    "@testing-library/user-event": "^12.2.2",
    "axios-mock-adapter": "^1.19.0",
    "babel-eslint": "10.1.0",
    "cypress": "^8.0.0",
    "eslint": "^7.24.0",
```

#### Verify Cypress works

After the initial install is done, we'll make sure it worked.

In your terminal, inside of the `client/` folder, type the following command:

```shell
yarn run cypress open
```

If everything goes according to plan, your terminal should recognize that this is the first time Cypress is fired up.

![Welcome message the first time Cypress is run in a project](https://d2uusema5elisf.cloudfront.net/courses/newline-guide-to-modernizing-an-enterprise-react-app/module_09/lesson_09.02/public/assets/cypress-terminal-welcome.png)

And after the welcome message, a new window containing the Cypress Test Runner should automatically open up and look something like this.

![Cypress automated test runner](https://d2uusema5elisf.cloudfront.net/courses/newline-guide-to-modernizing-an-enterprise-react-app/module_09/lesson_09.02/public/assets/cypress-test-runner.png)

A nice, new inclusion in addition to the Cypress Test Runner itself is a whole suite of predefined tests showing how to do various different types of tests with Cypress.

T> **Don't discount the example files**
T>
T> This wasn't available when I first started using Cypress, but luckily, the documentation and examples have been good since the start.
T>
T> But if you were ever wondering how to do something and wanted a quick reference in actual tests you can modify, these samples are pretty helpful.

If you'd like to see the test runner in action, go ahead and click the **Run** button. This will kick off all the preconfigured tests and give you a taste of how Cypress operates.

A little later in this lesson, we'll go over all the various pieces of code that go into making these tests work and how they're organized.

#### npm scripts

With Cypress installed in our project, it's time to add a few scripts to our `package.json` to make it easier to run Cypress in a browser that's visible to us for active development and debugging and to run Cypress in "headless" mode — the same way it would run for in a CI build pipelines.

Inside of our `client/` folder's `package.json` file, add the following two commands to our `"scripts"` section.

```json { actualFilename=./protected/source_code/hardware-handler-8-ending/client/package.json endLine=31 startLine=28 statedFilename=client/package.json url=https&#x3A;//gitlab.com/fullstackio/books/newline-guide-to-modernizing-an-enterprise-react-app/module_09/lesson_09.02/protected/source_code/hardware-handler-8-ending/client/package.json#L28 }
    "lint:fix": "eslint src/ --fix",
    "cypress:open": "cypress open",
    "cypress:run": "cypress run"
  },
```

**cypress:open**

Our first new script: `"cypress:open"` does just what we did manually from the command line a section ago: it opens the Cypress test runner browser so that we can interact with our tests.

In addition to being able to debug and test code in the browser, this test runner lets us be very targeted and specific about which test suites we want to run.

For instance, if you're only adding tests to one particular suite (or know that the code you changed should only impact the functionality for one set of tests), you can select only those tests to run in the interactive test runner instead of waiting for them all to run (which is what happens by default in headless mode).

Paige Niedringhaus

Like I was saying in the previous lesson, Cypress is really light years ahead

of all the other end-to-end testing frameworks out there.

And this even applies to its setup and integration into existing projects as

This lesson will focus on adding Cypress to our React application and config

uring it to run tests, both in headless and headed mode, depending on the need.

Need a fresh copy of the sample app before we begin our end-to-end testing? You

We'll need to add Cypress as a dev dependency to hardware handler before we can

start to take advantage of its capabilities.

So, open up a new terminal instance and run the following command to install

We're going to do inside of our client folder, YarnAddCypress-dev.

The first time that you install it, it will take a minute. There's a lot of

good info, demos, and configurations that come along with the Cypress install,

When it's done successfully, you'll see the new Cypress library in your package

So now, once it is installed, we see Cypress right here. Very good.

So after the initial install is done, we're going to make sure that it worked.

In your terminal inside of the client folder, type the following command. Yarn

If everything goes according to plan, your terminal should recognize that this

And after the welcome message, a new window containing the Cypress test runner

should automatically open up, and it will look something like this.

We have all sorts of integration tests, some getting started things, and then

A nice new inclusion in addition to the Cypress test runner itself is a whole

suite of predefined tests showing you how to do various different types of

And I want to recommend that you don't discount these sample files.

This wasn't available when I first started using Cypress, but luckily the

documentation and the examples have been good since the start.

But if you were ever wondering how to do something and wanted a quick reference

in actual tests that you can modify, these samples are very helpful.

So if you'd like to see the test runner in action, go ahead and click the Run

This is going to kick off all the pre-configured tests and give you a taste of

A little later in this lesson, we'll go over all the various pieces of code

that go into making these tests work and how they're organized.

Here is an example of a Cypress test running.

It went through it super quickly, but that is exactly what it does. It opens up

a browser and it runs through all the things that you tell it to.

And we are going to do a little bit of setup for ourselves.

So you can go ahead and close out of this for now.

And with Cypress installed in our project, it's time to add a few scripts to

our package JSON to make it easier to run Cypress in a browser that's visible

And to run Cypress in headless mode, the same way it would run in a CI build

Inside of our client folders package JSON, add the following two commands to

And the command for that will just be Cypress open.

And we are going to run to add Cypress run.

The command for that, which is Cypress run.