jest-image-snapshot

Jest matcher that performs image comparisons using Blink-diff and behaves just like Jest snapshots do! Very useful for browser visual comparison testing.

Installation:

npm i --save-dev jest-image-snapshot

Please note that Jest 20.x.x is a peerDependency. jest-image-snapshot will not work with anything below jest 20.x.x

Usage:

Extend Jest's expect

  const { toMatchImageSnapshot } = require('jest-image-snapshot');

  expect.extend({ toMatchImageSnapshot });

Use toMatchImageSnapshot() in your tests!

it('should demonstrate this matcher`s usage', () => {
  ...
  expect(image).toMatchImageSnapshot();
});

Optional configuration:

toMatchImageSnapshot() takes an optional options object where you can provide your own blink-diff configuration parameters and/or a custom snapshot identifier string and/or forcing no styled output for possibly storing the results in a file:

  it('should demonstrate this matcher`s usage with a custom blink-diff config', () => {
    ...
    const blinkDiffConfig = { perceptual: true };
    expect(image).toMatchImageSnapshot({ 
      customDiffConfig: blinkDiffConfig, 
      customSnapshotIdentifier: 'customSnapshotName', 
      noColors: true // the default is false
    });
  });

Any blink-diff custom configuration can be provided so long as the values for imageAPath, imageA, imageBPath, imageB, or imageOutputPath are not changed as these are used internally.

How it works

Given an image (should be either a PNGImage instance or a Buffer instance with PNG data) the toMatchImageSnapshot() matcher will create a __image_snapshots__ directory in the directory the test is in and will store the baseline snapshot image there on the first run.

On subsequent test runs the matcher will compare the image being passed against the stored snapshot.

To update the stored image snapshot run jest with --updateSnapshot or -u argument. All this works the same way as Jest snapshots.

See it in action

Typically this matcher is used to for visual tests that run on a browser. For example let's say I finish working on a feature and want to write a test to prevent visual regressions:

  it('renders correctly', async () => {
    const browser = await launchChromeHeadless();
    await browser.goTo('https://localhost:3000');
    const screenshot = await browser.takeScreenshot();

    expect(screenshot).toMatchImageSnapshot();
  });

Then after a few days as I finish adding another feature to my component I notice one of my tests failing!

Oh no! I must have introduced a regression! Let's see what the diff looks like to identify what I need to fix:

And now that I know that I broke the card art I can fix it!

Thanks jest-image-snapshot, that broken header would not have looked good in production!

Contributing

We welcome Your interest in the American Express Open Source Community on Github. Any Contributor to any Open Source Project managed by the American Express Open Source Community must accept and sign an Agreement indicating agreement to the terms below. Except for the rights granted in this Agreement to American Express and to recipients of software distributed by American Express, You reserve all right, title, and interest, if any, in and to Your Contributions. Please fill out the Agreement.

Please feel free to open pull requests and see CONTRIBUTING.md for commit formatting details.

License

Any contributions made under this project will be governed by the Apache License 2.0.

Code of Conduct

This project adheres to the American Express Community Guidelines. By participating, you are expected to honor these guidelines.

arivua / jest-image-snapshot