jest is a free, open source testing & quality assurance project written in TypeScript and released under MIT. It has 45,560 GitHub stars, 6,734 forks and 228 open issues, and was last pushed 16 hours ago. On this registry it ranks #3 of 7 tracked projects in Testing & Quality Assurance, with 5 head-to-head comparisons available.

What is jest?

Jest is a delightful, developer-ready JavaScript testing framework for writing and running tests in JavaScript and TypeScript projects.

What it is

Jest is a testing framework for JavaScript projects, maintained in TypeScript and released under the MIT licence. It provides a complete testing solution that works out of the box for most JavaScript projects, combining a test runner, assertion library, and watch mode in a single tool that requires little or no configuration before a first test can be written.

The concrete problem Jest solves is the setup overhead and slow feedback of assembling a JavaScript test stack from separate parts. Rather than wiring together a runner, an assertion library, and a file-watching mode yourself, you add jest as a development dependency, add "test": "jest" to your package.json, and start writing tests using test and expect. Its watch mode runs only the test files related to files that have changed, so a change is reflected in the results immediately.

Key capabilities

  • Runs in interactive watch mode that executes only test files related to changed files for fast feedback during development.
  • Supports snapshot testing, capturing snapshots of large objects to simplify testing and to analyse how they change over time.
  • Provides matchers such as expect and toBe for asserting that two values are exactly identical, with a broader matcher set documented under "Using Matchers".
  • Runs from the command line with options such as filtering files by name and specifying a configuration file, for example jest my-test --notify --config=config.json, which also displays a native OS notification after the run.
  • Generates a basic configuration file interactively with yarn create jest, asking questions about the project and writing an option with a short description for each.
  • Integrates with Babel through babel-jest, @babel/core, and @babel/preset-env, and honours Jest-aware Babel configuration via api.env('test').
  • Jest sets process.env.NODE_ENV to 'test' when it is not already set, allowing conditional compilation setup.

Who uses it and how

  • JavaScript project teams that add Jest as a dev dependency and wire it into package.json as "test": "jest" so that yarn test or npm test runs the suite.
  • Teams using Babel for transpilation, who install babel-jest, @babel/core, and @babel/preset-env and create a babel.config.js targeting the current Node version.
  • Projects built with webpack, Vite, Parcel, or TypeScript, each of which has a dedicated configuration section in the documentation.
  • Developers who install Jest globally with yarn global add jest or npm install jest --global and invoke the jest CLI directly from anywhere in their PATH.
  • Teams running tests in CI that rely on snapshot testing to track how large object outputs change over time.

Getting started

Install Jest as a development dependency with yarn add --dev jest or npm install --save-dev jest, add a "test": "jest" script to package.json, and run yarn test or npm test; alternatively generate a starter config with yarn create jest.

How it compares

The available facts name no comparable testing tools in this registry, so there is no basis for a direct comparison; Jest stands alone in this directory as a JavaScript testing framework under an MIT licence.

When to use it — and when not to

A self-hoster or adopter should be aware that the README's configuration guidance requires installing and configuring a transpiler such as Babel, including creating a babel.config.js and deciding which presets apply under api.env('test'), and that the project currently carries 228 open issues. Projects that need no transpilation setup or that use a different assertion model may find the framework heavier than necessary, though the MIT licence and the documented getting-started path keep the initial barrier low.

project readme (upstream, from github) — read inline

npm version Jest is released under the MIT license. Follow on Twitter

GitHub CI Status Coverage Status

Gitpod ready-to-code

 

🃏 Delightful JavaScript Testing

👩🏻‍💻 Developer Ready: A comprehensive JavaScript testing solution. Works out of the box for most JavaScript projects.

🏃🏽 Instant Feedback: Fast, interactive watch mode only runs test files related to changed files.

📸 Snapshot Testing: Capture snapshots of large objects to simplify testing and to analyze how they change over time.

See more on jestjs.io

Table of Contents

Getting Started

Install Jest using yarn:

yarn add --dev jest

Or npm:

npm install --save-dev jest

Note: Jest documentation uses yarn commands, but npm will also work. You can compare yarn and npm commands in the yarn docs, here.

Let's get started by writing a test for a hypothetical function that adds two numbers. First, create a sum.js file:

function sum(a, b) {
  return a + b;
}
module.exports = sum;

Then, create a file named sum.test.js. This will contain our actual test:

const sum = require('./sum');

test('adds 1 + 2 to equal 3', () => {
  expect(sum(1, 2)).toBe(3);
});

Add the following section to your package.json:

{
  "scripts": {
    "test": "jest"
  }
}

Finally, run yarn test or npm test and Jest will print this message:

PASS  ./sum.test.js
✓ adds 1 + 2 to equal 3 (5ms)

You just successfully wrote your first test using Jest!

This test used expect and toBe to test that two values were exactly identical. To learn about the other things that Jest can test, see Using Matchers.

Running from command line

You can run Jest directly from the CLI (if it's globally available in your PATH, e.g. by yarn global add jest or npm install jest --global) with a variety of useful options.

Here's how to run Jest on files matching my-test, using config.json as a configuration file and display a native OS notification after the run:

jest my-test --notify --config=config.json

If you'd like to learn more about running jest through the command line, take a look at the Jest CLI Options page.

Additional Configuration

Generate a basic configuration file

Based on your project, Jest will ask you a few questions and will create a basic configuration file with a short description for each option:

yarn create jest

Using Babel

To use Babel, install required dependencies via yarn:

yarn add --dev babel-jest @babel/core @babel/preset-env

Configure Babel to target your current version of Node by creating a babel.config.js file in the root of your project:

// babel.config.js
module.exports = {
  presets: [['@babel/preset-env', {targets: {node: 'current'}}]],
};

The ideal configuration for Babel will depend on your project. See Babel's docs for more details.

Making your Babel config jest-aware

Jest will set process.env.NODE_ENV to 'test' if it's not set to something else. You can use that in your configuration to conditionally setup only the compilation needed for Jest, e.g.

// babel.config.js
module.exports = api => {
  const isTest = api.env('test');
  // You can use isTest to determine what presets and plugins to use.

  return {
    // ...
  };
};

Note: babel-jest is automatically installed when installing Jest and will automatically transform files if a babel configuration exists in your project. To avoid this behavior, you can explicitly reset the transform configuration option:

// jest.config.js
module.exports = {
  transform: {},
};

Using webpack

Jest can be used in projects that use webpack to manage assets, styles, and compilation. webpack does offer some unique challenges over other tools. Refer to the webpack guide to get started.

Using Vite

Jest can be used in projects that use vite to serves source code over native ESM to provide some frontend tooling, vite is an opinionated tool and does offer some out-of-the box workflows. Jest is not fully supported by vite due to how the plugin system from vite works, but there is some working examples for first-class jest integration using the vite-jest, since this is not fully supported, you might as well read the limitation of the vite-jest. Refer to the vite guide to get started.

Using Parcel

Jest can be used in projects that use parcel-bundler to manage assets, styles, and compilation similar to webpack. Parcel requires zero configuration. Refer to the official docs to get started.

Using TypeScript

Jest supports TypeScript, via Babel. First, make sure you followed the instructions on using Babel above. Next, install the @babel/preset-typescript via yarn:

yarn add --dev @babel/preset-typescript

Then add @babel/preset-typescript to the list of presets in your babel.config.js.

// babel.config.js
module.exports = {
  presets: [
    ['@babel/preset-env', {targets: {node: 'current'}}],
+    '@babel/preset-typescript',
  ],
};

However, there are some caveats to using TypeScript with Babel. Because TypeScript support in Babel is purely transpilation, Jest will not type-check your tests as they are run. If you want that, you can use ts-jest instead, or just run the TypeScript compiler tsc separately (or as part of your build process).

Documentation

Learn more about using Jest on the official site!

Badge

Show the world you're using Jest → tested with jest jest tested jest

[![tested with jest](https://img.shields.io/badge/tested_with-jest-99424f.svg?logo=jest)](https://github.com/jestjs/jest)
[![jest tested](https://img.shields.io/badge/Jest-tested-eee.svg?logo=jest&labelColor=99424f)](https://github.com/jestjs/jest)
[![jest](https://jestjs.io/img/jest-badge.svg)](https://github.com/jestjs/jest)

Contributing

Development of Jest happens in the open on GitHub, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving Jest.

Code of Conduct

Facebook has adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.

Contributing Guide

Read our contributing guide to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to Jest.

Good First Issues

To help you get your feet wet and get you familiar with our contribution process, we have a list of good first issues that contain bugs which have a relatively limited scope. This is a great place to get started.

Credits

This project exists thanks to all the people who contribute.

Backers

Thank you to all our backers! 🙏

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website.

License

Jest is MIT licensed.

Copyright

Copyright Contributors to the Jest project.

Frequently asked questions

Is jest free to use?

jest is open source under the MIT licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does jest do?

Delightful JavaScript Testing.

What is jest written in?

jest is primarily written in TypeScript. Its source is publicly available at https://github.com/jestjs/jest, and it has 45,560 GitHub stars.