https://github.com/Hapag-Lloyd/jest-puppeteer-react

Screenshot tests for your react components in chromium using puppeteer & jest
https://github.com/Hapag-Lloyd/jest-puppeteer-react

Last synced: about 1 month ago
JSON representation

Screenshot tests for your react components in chromium using puppeteer & jest

• Host: GitHub
• URL: https://github.com/Hapag-Lloyd/jest-puppeteer-react
• Owner: Hapag-Lloyd
• License: mit
• Created: 2018-04-11T11:52:53.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2024-10-23T09:44:55.000Z (about 2 months ago)
• Last Synced: 2024-10-29T09:08:02.691Z (about 1 month ago)
• Language: JavaScript
• Size: 5.71 MB
• Stars: 71
• Watchers: 10
• Forks: 19
• Open Issues: 5
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-regression-testing - jest-puppeteer-react - Visual regression testing with Jest and puppeteer for React components (Tools and frameworks)
• awesome-regression-testing - jest-puppeteer-react - Visual regression testing with Jest and puppeteer for React components (Tools and frameworks)

README

        
# jest-puppeteer-react [![Build Status](https://travis-ci.com/Hapag-Lloyd/jest-puppeteer-react.svg?branch=master)](https://travis-ci.com/Hapag-Lloyd/jest-puppeteer-react)

```

yarn add jest-puppeteer-react

```

This lib combines `jest-puppeteer` with webpack and webpack-dev-server to render your React components so you don't have to setup a server and navigate to it. It also includes `jest-image-snapshot` which adds the `toMatchImageSnapshot` matcher to expect.

## Setup

1.  Use the preset in your jest configuration:

    ```

    {

      "preset": "jest-puppeteer-react"

    }

    ```

    Or require / include the needed scripts.

2.  Add a config file which contains a function to return a webpack config which is used to render:

    ```

    const webpack = require('webpack');

    const path = require('path');

    const buildDevWebpackConfig = require('./packages/core/dev/webpack/dev');

    module.exports = {

        generateWebpackConfig: function generateWebpackConfig(entryFiles, aliasObject) {

            const webpackConfig = buildDevWebpackConfig('test', {

                root: __dirname,

                app: 'x',

            }, {

                template: path.join(__dirname, './packages/dev-test-lib/screenshot/index.ejs'),

            }, webpack);

            webpackConfig.entry = { test: entryFiles };

            webpackConfig.resolve.alias = aliasObject;

            return webpackConfig;

        },

        port: 1111,

    };

    ```

## Usage

Then use the specified render in your tests:

```ecmascript 6

import React from 'react';

import { render } from 'jest-puppeteer-react';

import Button from '../Button';

describe('Button', () => {

    test('should render a button', async () => {

        await render(

            Button,

            { viewport: { width: 100, height: 100 } }

        );

        const screenshot = await page.screenshot();

        expect(screenshot).toMatchImageSnapshot();

    });

});

```

## Options

The second argument of render takes some options to make things easier. You can also supply a default for this via the config.

```

{

    timeout: 60000, // 60 seconds

    viewport: {

        width: 100,

        height: 100,

        deviceScaleFactor: 2 // Retina Resolution

    }

}

```

### Viewport

Automatically calls `page.setViewport()` for you.

See [puppeteer](https://github.com/GoogleChrome/puppeteer/blob/master/docs/api.md#pagesetviewportviewport) docs for options.

## Configuration

You can put a `jest-puppeteer-react.config.js` file in your project root which gets automatically detected by jest-puppeteer-react.

Example:

```

const webpack = require('webpack');

const path = require('path');

const buildDevWebpackConfig = require('./packages/core/dev/webpack/dev');

module.exports = {

    generateWebpackConfig: function generateWebpackConfig(entryFiles, aliasObject) {

        const webpackConfig = buildDevWebpackConfig('test', {

            root: __dirname,

            app: 'x',

        }, {

            template: path.join(__dirname, './packages/dev-test-lib/screenshot/index.ejs'),

        }, webpack);

        webpackConfig.entry = { test: entryFiles };

        webpackConfig.resolve.alias = aliasObject;

        return webpackConfig;

    },

    port: 1111,

    renderOptions: {

        viewport: { deviceScaleFactor: 2 },

        dumpConsole: false, // set to true to dump console.* from puppeteer

        // function calls before page.goto()

        before: async (page) => {

            // for example, disable cache

            await page.setCacheEnabled(false);

        },

        // function calls after page.goto()

        after: (page) => {},

    },

};

```

### Configure Puppeteer

You can put a `jest-puppeteer.config.js` file in your root to configure puppeteer. This is a feature of the jest-puppeteer lib. See their readme for documentation: [jest-puppeteer](https://github.com/smooth-code/jest-puppeteer/tree/6cd3050e472c9a8bcdb18e2635a40ad674c4b795#configure-puppeteer).

### Configure ESLint

If you want to use the page object directly (without using the return value of render), you can set it as a global for eslint. See [jest-puppeteer](https://github.com/smooth-code/jest-puppeteer/tree/6cd3050e472c9a8bcdb18e2635a40ad674c4b795#configure-eslint) for an example.

## Limitations

To be able to render the components in the browser, the test cases are required via webpack and the structure functions such as describe and test are evaluated. However, special behavior implemented in jest may be missing. For example mocks and timers are not supported currently.

Furthermore at the moment hooks are not supported aswell. But they could be implemented quite easily.