Wherever you are at with code coverage you generally don’t want that level to go down. Let’s add coverage thresholds globally as well as in specific files to ensure we never drop below a certain level of coverage.

Configure Jest for Testing JavaScript Applications

Set a Code Coverage Threshold in Jest to Maintain Code Coverage Levels

Instructor: [00:01] As you start adding tests to your code base, it would be really nice if you make sure that people don't actually code that reduces the amount of code coverage that you have in your project, because you're working toward improving the code coverage in your project.

[00:14] For example, this utilities file, maybe that's really important and you don't want to drop the level of coverage in this utilities file by somebody add a new function that isn't tested.

[00:24] What we're going to do here to make that happen is, I'm going to add a coverage threshold. We want our global coverage threshold to have certain elements. Here, we have the statements, branches, functions and lines. Those are the four elements of code coverage.

[00:39] I'm going to say, "Statements, we want 100 percent, branches 100 percent, functions 100 percent, and lines 100 percent."

```js
 setupFilesAfterEnv: ['@testing-library/jest-dom/extend-expect'],
  snapshotSerializers: ['jest-emotion'],
  coverageThreshold: {
    global: {
      statements: 100,
      branches: 100,
      functions: 100,
      lines: 100,
    },
  },
}
```


Let's see what happens if I run the test scripts with coverage here. We're going to get a bunch of errors saying, "Hey, the global coverage threshold for statements was not met." The same for branches lines and functions.

[01:01] Let's add something that's maybe a little bit more reasonable. I typically like to do a couple percentage points lower than what we have currently so that as changers are made and things, we have a little bit of flexibility here. I'm going to go ahead and for our statements, we'll do 34 percent.

[01:17] For our branches, we'll do 24 percent. For our lines, let's do 34. For our functions, we'll do 29. 

```js
 setupFilesAfterEnv: ['@testing-library/jest-dom/extend-expect'],
  snapshotSerializers: ['jest-emotion'],
  coverageThreshold: {
    global: {
      statements: 34,
      branches: 24,
      functions: 34,
      lines: 29,
    },
  },
}
```

Now, we can `npm t` to run our test again. Our test script almost passes. It looks like I mistyped this. It should be 31 on our function. Let's do 29 on this funtions. 

```js
    global: {
      statements: 34,
      branches: 24,
      functions: 29,
      lines: 29,
    },
```


Now, we run `npm t` again. Our tests are indeed passing.

[01:42] Now, as people add new code to our code base, they need to make sure they add some test so that they don't break this coverage threshold and ultimately break the build. Now, one really important thing about coverage to remember is that it's not a perfect metric for confidence.

[01:56] The problem is that not all lines in your code base are equal. For example, maybe this utilities file is super, super important because it's used just all over the place. The autoscaling text has this line here that's really not that important, it doesn't happen all that often. Even if that were to happen, it's not a huge deal that that gets broken as an example.

[02:16] These lines that are being missed or hit in our test are not completely equal. Let's say that you had one file, for example, this utils file. You just really wanted to make sure you never drop coverage on this. What we're going to do is we're going to specify an additional property. That property is a glob that matches the file that we want to make sure we never break.

[02:36] Here, we'll say source-shared-utils.js and with this, we're going to say we want our statements to stay at a hundred percent. Right now, the branches are at 80, so we'll just leave that where it is. Functions are at 100 and lines are at 100. Hopefully one day, somebody can add some test to increase the branches coverage.

```js
 setupFilesAfterEnv: ['@testing-library/jest-dom/extend-expect'],
  snapshotSerializers: ['jest-emotion'],
  coverageThreshold: {
    global: {
      statements: 34,
      branches: 24,
      functions: 29,
      lines: 29,
    },
    './src/shared/utils.js': {
      statements: 100,
      branches: 80,
      functions: 100,
      lines: 100,
    },
  },
}
```

[02:57] Now if I `npm t`, I'm actually going to get a failure even though my utils is totally covered. The reason I'm getting that failure is because now my global coverage threshold has dropped. That's because when you start adding the specific files for the coverage threshold, that reduces the global coverage threshold because Jest will actually pull that coverage out of your total numbers.

[03:22] Let's go ahead and we'll change our statements to bring it down to a 31 and our branches will bring that down to 18. 

```js
 setupFilesAfterEnv: ['@testing-library/jest-dom/extend-expect'],
  snapshotSerializers: ['jest-emotion'],
  coverageThreshold: {
    global: {
      statements: 31,
      branches: 18,
      functions: 29,
      lines: 29,
    },
    './src/shared/utils.js': {
      statements: 100,
      branches: 80,
      functions: 100,
      lines: 100,
    },
  },
}
```

We'll save that, run `npm t` and our test are all passing.

[03:34] Let's see what happens if we mess up our utilities coverage by updating the branches to 100 percent. 

```js
 './src/shared/utils.js': {
      statements: 100,
      branches: 100,
      functions: 100,
      lines: 100,
    },
```

We haven't made it to 100 percent and it tells us specifically the coverage for files mentioned in this glob is not meeting the coverage threshold of 100 percent for branches.

[03:51] We get a really clear picture of which one of the files we need to add coverage for. We fixed that NMP run are a test again here. We've run all of our test suites and the coverage numbers are being met.

[04:03] On review, to make sure that we maintain our coverage threshold, we added this coverage threshold property that has a global coverage numbers set to something that is relatively close to where we are today. We can improve this overtime and increase this as we increase our code coverage in our project. We can also specify some specific files that we want to maintain a higher code coverage on.

```js
 setupFilesAfterEnv: ['@testing-library/jest-dom/extend-expect'],
  snapshotSerializers: ['jest-emotion'],
  coverageThreshold: {
    global: {
      statements: 15,
      branches: 10,
      functions: 15,
      lines: 15,
    },
    './src/shared/utils.js': {
      statements: 100,
      branches: 80,
      functions: 100,
      lines: 100,
    },
  },
}
```


Jest is a fully featured testing framework with a developer experience that is second to none. It’s remarkably simple and flexible at the same time. For simple use cases, you often don’t need to configure anything, install and enjoy the built-in coverage and watch mode support.

In a real-world application though, you’ll often have needs specific to your application, especially when testing browser-based applications. You'll need to handle Webpack loaders, dynamic imports, and custom module resolution which Node.js does not support.

In this course we’ll go over ways you can optimize your Jest configuration to make testing real-world JavaScript applications a delight. We’ll cover what’s already been mentioned in addition to Babel support, code coverage, how to make watch mode even more helpful, and how to run test suites with entirely different configurations.

Intro to Configure Jest for Testing JavaScript Applications

We start in a small, but real-world application that’s built with webpack and React. We’ll go over installing the Jest testing framework locally to our project, adding an npm script to make it easy to run, and adding an example test file.

Install and Run Jest

Jest automatically loads and applies our babel configuration. However, because our project takes advantage of tree shaking with webpack, our babel configuration disables compiling modules. For Jest to work on our code, we need to make sure that our babel configuration compiles modules during our tests. We’ll use the NODE_ENV environment variable to generate the proper configuration.

Compile Modules with Babel in Jest Tests

In our application we’re testing code that should run in the browser, but Jest is intended to test JavaScript that runs in the browser or in node. Let’s create a custom jest config file so we can customize the test environment.

Configure Jest’s Test Environment for Testing Node or Browser Code

In most real-world applications using webpack, you’re likely using a few loaders. In this lesson we’ll see how to make Jest load our modules properly with a moduleNameMapper so we can test our code that makes use of these loaders.

Support Importing CSS files with Jest’s moduleNameMapper

If you’re using CSS modules with webpack, then we can improve our moduleNameMapper to improve our experience and capabilities testing our components by including the css module property name in our tests using identity-obj-proxy.

Support using Webpack CSS Modules with Jest

Snapshot testing is a way to simplify writing and maintaining assertions. As noted in [the Jest documentation](http://jestjs.io/docs/en/snapshot-testing.html#snapshot-testing-with-jest): “The snapshot artifact should be committed alongside code changes, and reviewed as part of your code review process. Jest uses pretty-format to make snapshots human-readable during code review. On subsequent test runs Jest will simply compare the rendered output with the previous snapshot. If they match, the test will pass. If they don't match, either the test runner found a bug in your code that should be fixed, or the implementation has changed and the snapshot needs to be updated.” Let’s see how these work and in what situations we can and should use them.

This lesson uses a simple demo before hopping into the application code testing DOM nodes. This example code isn't available.

Generate a Serializable Value with Jest Snapshots

Part of the power of snapshots is the ability to provide custom serializers. Let’s check out how to use jest-emotion to include our emotion CSS styles in our React component snapshots so we can be made aware of the impact of our CSS changes on our components.

UPDATE: `jest-emotion` has been renamed to `@emotion/jest` and you add the serializer with `'@emotion/jest/serializer'` instead of simply `'jest-emotion'`.

Test an Emotion Styled UI with Custom Jest Snapshot Serializers

Webpack’s resolve.modules configuration is a great way to make common application utilities easily accessible throughout your application. We can emulate this same behavior in Jest using the moduleDirectories configuration option.

Support Custom Module Resolution with Jest moduleDirectories

Often you’ll have some setup that you want to run before your tests start. Let’s see how we can use the setupFilesAfterEnv configuration in Jest to take care of test boilerplate and establish a good testing environment for our tests.

Configure Jest to Run Setup for All Tests with Jest setupFilesAfterEnv

Every large testbase has common utilities that make testing easier to accomplish. Whether that be a custom render function or a way to generate random data. Let’s see how we can make accessing these custom utilities throughout the tests easier using Jest’s moduleDirectories feature.

Support a Test Utilities File with Jest moduleDirectories

As the codebase grows it makes our test runs take longer and longer. Naturally people will run the tests less frequently to avoid waiting. With Jest’s powerful and interactive watch mode we can easily run the tests that we want to focus on without having to run all the tests in the codebase.

Use Jest Watch Mode to Speed Up Development

Sometimes it can be a real challenge to determine what’s going on when testing your code. It can be really helpful to step through your code in a debugger. In this lesson we’ll see how to use Jest’s --runInBand flag with node’s --inspect-brk to debug our tests in Chrome’s debugger.

Step through Code in Jest using the Node.js Debugger and Chrome DevTools

Jest comes with code coverage reporting built-into the framework, let’s see how quick and easy it is to add code coverage reporting to our project and take a look at the generated report. 

Configure Jest to Report Code Coverage on Project Files

You may have an idea of what Code Coverage is, but let’s take a quick look at how it’s recorded so we can understand how to analyze code coverage reports.

Analyze Jest Code Coverage Reports

The coverage report generated by Jest is fantastic, but it’d be great to track that coverage over time and be able to review that coverage at a glance, maybe even put it up on a display in the office! Codecov.io is a fantastic service that can consume our code coverage report and it integrates great with GitHub. Let’s see how we can extend our existing Travis build configuration to send the coverage report to Codecov.io.

Report Jest Test Coverage to Codecov through TravisCI

In CI, we don’t want to start the tests in watch mode, but locally we normally want to run the tests in watch mode. We can have separate scripts, but it’d be great to not have to remember which script to run locally. Let’s use is-ci-cli to run the right script in the right environment when running the test script.

Run Jest Watch Mode by Default Locally with is-ci-cli

Sometimes you may have situations where configuration needs to be different for certain tests. In this lesson we’ll take a look at how we could create a custom configuration for tests that are intended to run in a node environment.

Run Tests with a Different Configuration using Jest’s --config Flag and testMatch Option

Sometimes you may find it useful to have more than one configuration in a project (for example, running some tests in a node environment and others in the jsdom environment). In this lesson we’ll learn about Jest’s projects feature to have jest run both of these configurations at once.

Support Running Multiple Configurations with Jest’s Projects Feature

Jest is more than a testing framework. It’s a highly optimized, blazing fast platform with incredible parallelization for running tasks across many files in our project. It has a capability to run more than just tests. We can bring these features to our linting as well. Let’s see how we can bring our favorite Jest features (like watch mode) to ESLint with jest-runner-eslint.

Run ESLint with Jest using jest-runner-eslint

It’s great that we can run multiple projects in our watch mode and that we can scope the tests down to specific tests, but sometimes it’s nice to be able to quickly switch between projects in watch mode. Let’s see how this works with jest-watch-select-projects.

Test Specific Projects in Jest Watch Mode with jest-watch-select-projects

Jest’s watch mode is [pluggable](http://jestjs.io/docs/en/watch-plugins.html) and jest-watch-typeahead is one plugin that you definitely don’t want to live without. It enhances the watch mode experience to help you know which tests will be run based on your filter. Making it even easier to run only the tests you’re concerned with running as you develop your codebase.

Filter which Tests are Run with Typeahead Support in Jest Watch Mode

Running the project tests on commit is a great way to avoid breaking the application accidentally and leverage the mechanism for confidence you have from your testbase. However, as the testbase grows this can take a very long time and slow productivity down. Let’s see how Jest is capable of running only the tests and linting only the files that are affected by the files we’re committing with husky and lint-staged to speed up our local test runs as well as help us avoid accidentally committing code that breaks our application.

Set a Code Coverage Threshold in Jest to Maintain Code Coverage Levels

Transcript

Set a Code Coverage Threshold in Jest to Maintain Code Coverage Levels