Skip to content

Latest commit

 

History

History
195 lines (130 loc) · 10.1 KB

README.md

File metadata and controls

195 lines (130 loc) · 10.1 KB

Jest

🃏 Delightful JavaScript Testing

CircleCI Build Status Travis Build Status Windows Build Status Codecov badge npm version SemVer Blazing Fast

Backers on Open Collective Sponsors on Open Collective PR's welcome License: MIT Known Vulnerabilities

Follow on Twitter

👩🏻‍💻 Developer Ready: Complete and ready to set-up JavaScript testing solution. Works out of the box for any React project.

🏃🏽 Instant Feedback: Fast interactive watch mode runs only test files related to changed files and is optimized to give signal quickly.

📸 Snapshot Testing: Capture snapshots of React trees or other serializable values to simplify testing and to analyze how state changes over time.

Getting Started

Install Jest using yarn:

yarn add --dev jest

Or via npm:

npm install --save-dev jest

The minimum supported Node version is v6.0.0 by default. If you need to support Node 4, refer to the Compatibility issues section.

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 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) with 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

Using Babel

To use Babel, install the babel-jest and @babel/core packages:

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

Don't forget to add a babel.config.js file in your project's root folder. For example, if you are using ES6 and React.js with the @babel/preset-env and @babel/preset-react presets:

module.exports = {
  presets: ['@babel/preset-env', '@babel/preset-react'],
};

You are now set up to use all ES6 features and React specific syntax.

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:

// package.json
{
  "jest": {
    "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 TypeScript

To use TypeScript in your tests install @babel/preset-typescript and add it to your Babel config.

Documentation

Learn more about using Jest on the official site!

Badge

Show the world you're using Jesttested with jest jest

[![tested with jest](https://img.shields.io/badge/tested_with-jest-99424f.svg)](https://github.com/facebook/jest) [![jest](https://jestjs.io/img/jest-badge.svg)](https://github.com/facebook/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.

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.

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.

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.

Thank you to all our backers! 🙏

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

License

Jest is MIT licensed.