chai-jest-snapshot

Chai assertion for jest-snapshot. See Jest 14.0: React Snapshot Testing for background knowledge about snapshot testing.

Installation

On the command line:

$ npm install --save-dev chai-jest-snapshot

Usage

There are four different ways to use chai-jest-snapshot.

Mocha Configuration Mode (Recommended for Mocha Users)

If you are using mocha as your test runner, it is recommended to use chai-jest-snapshot in "mocha configuration mode".

Note: do not use an arrow function for the beforeEach as these will not receive the correct this value provided by mocha.

In your test setup file:

1import chai from "chai";
2import chaiJestSnapshot from "chai-jest-snapshot";
3
4chai.use(chaiJestSnapshot);
5
6before(function() {
7  chaiJestSnapshot.resetSnapshotRegistry();
8});
9
10beforeEach(function() {
11  chaiJestSnapshot.configureUsingMochaContext(this);
12});

In your spec file(s) (as an example):

1import React from "react";
2import renderer from "react-test-renderer";
3import { expect } from "chai";
4import Link from "./Link";
5
6describe("Link", function() {
7  it("renders correctly", () => {
8    const tree = renderer.create(
9      <Link page="http://www.facebook.com">Facebook</Link>
10    ).toJSON();
11    expect(tree).to.matchSnapshot();
12  });
13});

This will automatically write snapshots to a file with the same name as your test file, with .snap added to the end. This will also choose snapshot names based on the test name, adding a number to the end based on the number of times matchSnapshot was called in each test (similar to jest).

In this mode, to update a single snapshot, you can pass true as an argument to matchSnapshot:

1expect(tree).to.matchSnapshot(true);

If you want to update all snapshots without adding true to each one, set the environment variable CHAI_JEST_SNAPSHOT_UPDATE_ALL to "true":

1# assuming `npm test` runs your tests:
2# sh/bash/zsh
3$ CHAI_JEST_SNAPSHOT_UPDATE_ALL=true npm test
4# fish
5$ env CHAI_JEST_SNAPSHOT_UPDATE_ALL=true npm test

This behaves similarly to running jest -u.

If you want tests to fail when a snapshot is missing (instead of writing a new one), set the environment variable CI to "true":

1# assuming `npm test` runs your tests:
2# sh/bash/zsh
3$ CI=true npm test
4# fish
5$ env CI=true npm test

This behaves similarly to running jest --ci.

Jest Configuration Mode (Recommended for Jest Users)

If you are using Jest, but prefer Chai assertions, you don’t have anything to configure except loading the plugin itself: the matchSnapshot Chai assertion will automatically delegate to Jest’s built-in snapshot capability, so all usual options, settings, CLI flags, method arguments, etc. will work out of the box.

1import chai from "chai";
2import chaiJestSnapshot from "chai-jest-snapshot";
3
4chai.use(chaiJestSnapshot);

Framework-agnostic Configuration Mode (Recommended for Non-Mocha/Jest Users)

If you are using neither mocha nor Jest as your test runner, it is recommended to use chai-jest-snapshot in "framework-agnostic configuration mode".

In your test setup file:

1import chai from "chai";
2import chaiJestSnapshot from "chai-jest-snapshot";
3
4chai.use(chaiJestSnapshot);
5
6before(function() {
7  // In order for watch mode to work correctly, the snapshot registry needs to
8  // be reset at the beginning of each suite run. In mocha, `before` callbacks
9  // are called before the whole suite runs, but in other test runners you may
10  // need to run this somewhere else; for example, in jasmine, you'd put it in a
11  // `beforeAll` instead of `before`.
12  chaiJestSnapshot.resetSnapshotRegistry();
13});

In your spec file(s) (as an example):

1import React from "react";
2import renderer from "react-test-renderer";
3import { expect } from "chai";
4import Link from "./Link";
5
6describe("Link", function() {
7  beforeEach(function() {
8    chaiJestSnapshot.setFilename(__filename + ".snap");
9  });
10
11  it("renders correctly", () => {
12    // There may be a way to automate this in your test runner; for example,
13    // getting the test name in the beforeEach callback, or using a custom
14    // reporter to hook into the test lifecycle.
15    chaiJestSnapshot.setTestName("Link renders correctly");
16
17    const tree = renderer.create(
18      <Link page="http://www.facebook.com">Facebook</Link>
19    ).toJSON();
20    expect(tree).to.matchSnapshot();
21  });
22});

This will write snapshots to the file name you specify, (in this example, a file with the same name and location as the spec file, but with .snap added to the end). This will use whatever snapshot name you specify as a template, adding a number to the end based on the number of times matchSnapshot was called using the same file name and snapshot name (similar to what jest does).

In this mode, to update a single snapshot, you can pass true as an argument to matchSnapshot:

1expect(tree).to.matchSnapshot(true);

If you want to update all snapshots without adding true to each one, set the environment variable CHAI_JEST_SNAPSHOT_UPDATE_ALL to "true":

1# assuming `npm test` runs your tests:
2# sh/bash/zsh
3$ CHAI_JEST_SNAPSHOT_UPDATE_ALL=true npm test
4# fish
5$ env CHAI_JEST_SNAPSHOT_UPDATE_ALL=true npm test

This behaves similarly to running jest -u.

If you want tests to fail when a snapshot is missing (instead of writing a new one), set the environment variable CI to "true":

1# assuming `npm test` runs your tests:
2# sh/bash/zsh
3$ CI=true npm test
4# fish
5$ env CI=true npm test

This behaves similarly to running jest --ci.

Manual Mode

If Mocha Configuration Mode or Framework-agnostic Configuration Mode do not satisfy your needs, you can use "manual mode".

In your test setup file:

1import chai from "chai";
2import chaiJestSnapshot from "chai-jest-snapshot";
3
4chai.use(chaiJestSnapshot);

In your spec file(s) (as an example):

1import React from "react";
2import renderer from "react-test-renderer";
3import { expect } from "chai";
4import Link from "./Link";
5
6describe("Link", function() {
7  it("renders correctly", () => {
8    const tree = renderer.create(
9      <Link page="http://www.facebook.com">Facebook</Link>
10    ).toJSON();
11
12    let snapshotFilename = __filename + ".snap";
13    let snapshotName = "Link renders correctly";
14    expect(tree).to.matchSnapshot(snapshotFilename, snapshotName);
15  });
16});

This will write snapshots to the file name you specify, (in this example, a file with the same name and location as the spec file, but with .snap added to the end). This will use whatever snapshot name you specify as the snapshot name. NOTE: unlike other modes, this mode does not add a number to the end of the snapshot name.

In this mode, to update a single snapshot, you can pass true as an extra, third argument to matchSnapshot:

1expect(tree).to.matchSnapshot(snapshotFilename, snapshotName, true);

If you want to update all snapshots without adding true to each one, set the environment variable CHAI_JEST_SNAPSHOT_UPDATE_ALL to "true":

1# assuming `npm test` runs your tests:
2# sh/bash/zsh
3$ CHAI_JEST_SNAPSHOT_UPDATE_ALL=true npm test
4# fish
5$ env CHAI_JEST_SNAPSHOT_UPDATE_ALL=true npm test

This behaves similarly to running jest -u.

If you want tests to fail when a snapshot is missing (instead of writing a new one), set the environment variable CI to "true":

1# assuming `npm test` runs your tests:
2# sh/bash/zsh
3$ CI=true npm test
4# fish
5$ env CI=true npm test

This behaves similarly to running jest --ci.

Tips

• If you are referencing __filename or __dirname in your snapshot file names, and compile your tests using babel, you will probably want to use babel-plugin-transform-dirname-filename to ensure your snapshots end up in your source directory instead of the directory where your tests were built (ie dist or build).

Contributing

$ npm install
$ npm test

Pull Requests and Issues welcome