We’re going to need a newly created user for several tests so let’s move our cy.request command to register a new user into a custom Cypress command so we can use that wherever we need a new user.

There's been a small breaking change to Cypress Testing Library that affects the code in this video. [Learn more here.](https://github.com/testing-library/cypress-testing-library/releases/tag/v6.0.0)

Install, Configure, and Script Cypress for JavaScript Web Applications

Use Custom Cypress Command for Reusable Assertions

Instructor: 00:00 I'm really glad we were able to reduce duplication between the login and the registration with the `createUser` command, but we do still have quite a bit of duplication between these two tests, which are verifying that the user was registered and logged in correctly.

00:13 I actually do want to have this duplication between these two because I could break something in the login process and not break that same thing in the registration, so I want to have the same assertions in here. What I'm going to do is I'll copy everything below our `url()` in `login.js`. We'll paste it in a comment under `Commands`.

#### commands.js
```js
/*
.url()
.should('eq', `${Cypress.config().baseUrl}/`)
.window()
.its('localStorage.token')
.should('be.a', 'string')
.findByTestId('username-display')
.should('have.text', user.username)
*/
```

00:28 Let's go ahead and make two assertions. The first one, we'll say `Cypress.Commands.add('assertHome', ... )`. This one, we'll just say `cy`, and then we'll bring up the `url()` and `should` stuff. Now, I can come in `login.js`, delete the `url` and `should` and say `.assertHome`. 

```js
Cypress.Commands.add('assertHome', () => {
  cy.url().should('eq', `${Cypress.config().baseUrl}/`)
})
```

We'll do the same thing for our `login`.

00:49 We want to take care of the stuff in the comment. Let's go ahead and make another command, `Cypress.Commands.add('assertLoggedInAs' ... )`, and then we'll just do `cy`. We'll bring in all this stuff.

01:03 We need the `user` by passing in `user` as an argument. We'll get rid of that empty comment. 

```js
Cypress.Commands.add('assertLoggedInAs', user => {
  cy.window()
    .its('localStorage.token')
    .should('be.a', 'string')
    .findByTestId('username-display')
    .should('have.text', user.username)
})
```

We'll save that and then come into `regiser.js` and swap all of what we put in our `add` command with `assertLoggedInAs`, and we'll pass the `user`. 

#### register.js
```js
describe('registration', () => {
  it('should register a new user', () => {
    const user = buildUser()
    cy.visit('/')
      .findByText(/register/i)
      .click()
      .findByLabelText(/username/i)
      .type(user.username)
      .findByLabelText(/password/i)
      .type(user.password)
      .findByText(/submit/i)
      .click()
      .assertHome()
      .assertLoggedInAs(user)
  })
  ...
})
```

We'll do the same thing for our `login.js`. 

#### login.js
```js
describe('login', () => {
  it('should login an existing user', () => {
    cy.createUser().then(user => {
      cy.visit('/')
        .findByText(/login/i)
        .click()
        .findByLabelText(/username/i)
        .type(user.username)
        .findByLabelText(/password/i)
        .type(user.password)
        .findByText(/submit/i)
        .click()
        .assertHome()
        .assertLoggedInAs(user)
    })
  })
})
```

Great. Now our tests are a lot more lean and descriptive. We can go over to our tests and see that they're all passing.

01:24 In review, what we did here is reduce some duplication and improve the readability of our tests by creating some custom commands to encapsulate some Cypress assertions and using those custom commands in our tests.

 is an incredibly powerful web testing tool. It’s capable of testing any web application. Its architecture places it a cut above similar end-to-end testing tools. Its developer experience is best-in-class. And because Cypress runs your tests in the same context as the rest of your application, you’re able to get speed, reliability, and debuggability that are just a long - distant dream with similar tools. The catch? There is no catch. Cypress is exceptional.

In this course, we’ll go over how you can install, configure, and script Cypress to test modern, real - world JavaScript web applications.

What's changed in Install, Configure, and Script Cypress for JavaScript Web Applications

Intro to Install, Configure, and Script Cypress for JavaScript Web Applications 

Despite the fact that Cypress is an application that runs natively on your machine, you can install it and add it as a dependency just like all other dependencies in your package.json file. So let's install Cypress and get our project ready to start end-to-end testing with Cypress.

Install and Run Cypress

Cypress starts out your project with a ton of tests, let’s remove those and add our first test that verifies our calculator can add two numbers together using the Cypress selector playground and Cypress commands.

Write the First Cypress Test

Cypress is fairly simple to configure, but it’s important to optimize our experience in testing Cypress. We’ll configure the baseUrl to make it easier to visit our app and we’ll also move our test files to a folder called e2e to make it more clear what types of tests we want to write with Cypress. We’ll use the cypress.json file, but Cypress can also be configured via command line flags and environment variables.

Configure Cypress in cypress.json

Our selectors are pretty ridiculous, mostly because we’re using CSS-in-JS and css modules for our react application. But even if we weren’t, using class names as selectors for our application testing is pretty brittle and not really testing in the way a user would. So instead let’s use cypress-testing-library to improve our selectors and make it easier to read our tests.

There's been a small breaking change to Cypress Testing Library that affects the code in this video. [Learn more here.](https://github.com/testing-library/cypress-testing-library/releases/tag/v6.0.0)

Installing Cypress Testing Library

We want to make starting cypress as simple as possible for local development and we need to be able to run a single script that exits when the tests are complete for continuous integration. So let’s add a few scripts to get ourselves setup for this development experience.

Script Cypress for Local Development and Continuous Integration

One of the greatest features of Cypress is how awesome the experience of debugging tests is. You do have to get used to the asynchronous nature of E2E testing, but once you get the hang of that debugging is pretty straightforward, and the ability to debug your own source code is awesome. The fact that your test and source code are executed in the same context also gives you some powerful advantages as well. You can potentially even expose some internal state to your Cypress app.

Debug a Test with Cypress

Let’s write a test to fill out our registration form. Because we’ll be running this against a live backend, we need to generate the user’s information to avoid re-runs from trying to create new users that already exist. There are trade-offs with this approach. You should probably also clean out the application database before all of your tests start (how you accomplish this is pretty application-specific). Also, if your application requires email confirmation, I recommend you mock that on the backend and automatically set the user as confirmed during tests.

There's been a small breaking change to Cypress Testing Library that affects the code in this video. [Learn more here.](https://github.com/testing-library/cypress-testing-library/releases/tag/v6.0.0)

 Test User Registration with Cypress

Because Cypress allows you to use all the developer tools you’re used to from Google Chrome, you can actually use Cypress as your main application development workflow. If you’ve ever tried to develop a feature that required you to be in a certain state you’ve probably felt the pain of repeatedly refreshing the page and clicking around to get into that state. Instead, you can use cypress to do that and developer your application entirely in Cypress.

There's been a small breaking change to Cypress Testing Library that affects the code in this video. [Learn more here.](https://github.com/testing-library/cypress-testing-library/releases/tag/v6.0.0)

Cypress Driven Development

Normally I prefer to test error states using integration or unit tests, but there are some situations where it can be really useful to mock out a response to test a specific scenario in an E2E test. Let’s use the cypress server and route commands to mock a response from our registration request to test the error state.

Simulate HTTP Errors in Cypress Tests

To test user login we need to have a user to login with. We could seed the database with a user and that may be the right choice for your application. In our case though we’ll just go through the registration process again and then login as the user and make the same assertions we made for registration.

There's been a small breaking change to Cypress Testing Library that affects the code in this video. [Learn more here.](https://github.com/testing-library/cypress-testing-library/releases/tag/v6.0.0)

Test User Login with Cypress

We’re duplicating a lot of logic between our registration and login tests and not getting any additional confidence, so lets reduce the duplicate logic and time in our tests using cy.request to get a user registered rather than clicking through the application to register a new user.

There's been a small breaking change to Cypress Testing Library that affects the code in this video. [Learn more here.](https://github.com/testing-library/cypress-testing-library/releases/tag/v6.0.0)

Create a User with cy.request from Cypress

Keep Tests Isolated and Focused with Custom Cypress Commands

For most applications you’re going to need to be logged in as a user to interact with the application. Let’s see how we can register as a new user and login as that user to test using the application as a logged in user.

There's been a small breaking change to Cypress Testing Library that affects the code in this video. [Learn more here.](https://github.com/testing-library/cypress-testing-library/releases/tag/v6.0.0)

Run Tests as an Authenticated User with Cypress

We’re duplicating a bunch of commands between our new test and the login test and it’s not giving us any more confidence that the application is working properly. So let’s do the same thing we did with registration and make a cy.request command to login with the newly created user to speed up our test and make it more focused.

There's been a small breaking change to Cypress Testing Library that affects the code in this video. [Learn more here.](https://github.com/testing-library/cypress-testing-library/releases/tag/v6.0.0)

Use cy.request from Cypress to Authenticate as a New User

It’s pretty likely that we’ll need to login as a particular user for many tests, let’s take our cy.request command and turn it into a custom command to make it easier for the places we’ll be needing a logged in user.

There's been a small breaking change to Cypress Testing Library that affects the code in this video. [Learn more here.](https://github.com/testing-library/cypress-testing-library/releases/tag/v6.0.0)

Use a Custom Cypress Command to Login as a User

Combine Custom Cypress Commands into a Single Custom Command

Because Cypress runs in a real Chrome browser, we can install extensions, like React DevTools. The tricky bit will be to make our application hook up to the extension properly.

Use Custom Cypress Command for Reusable Assertions

Transcript

Use Custom Cypress Command for Reusable Assertions