addon-storyshots-wdio

    5.3.10 • Public • Published

    storyshots-wdio

    Workflow status Version npm

    Adaptation of storyshots-puppeteer addon which uses WebdriverIO for a wider browser support.

    Getting Started

    Add the following module into your app.

    yarn add --dev addon-storyshots-wdio

    Configure Storyshots for image snapshots

    /*\ React-native is not supported by this test function.

    Internally, it uses jest-image-snapshot.

    When willing to generate and compare image snapshots for your stories, you have two options:

    • Have a storybook running (ie. accessible via http(s), for instance using yarn storybook)
    • Have a static build of the storybook (for instance, using yarn build-storybook)

    Then you will need to reference the storybook URL (file://... if local, http(s)://... if served)

    Using default values for imageSnapshots

    Then you can either create a new Storyshots instance or edit the one you previously used:

    import initStoryshots from '@storybook/addon-storyshots';
    import { imageSnapshot } from 'addon-storyshots-wdio';
     
    initStoryshots({ suite: 'Image storyshots', test: imageSnapshot() });

    This will assume you have a storybook running on at http://localhost:6006. Internally here are the steps:

    Specifying the storybook URL

    If you want to set specific storybook URL, you can specify via the storybookUrl parameter, see below:

    import initStoryshots from '@storybook/addon-storyshots';
    import { imageSnapshot } from 'addon-storyshots-wdio';
     
    initStoryshots({
      suite: 'Image storyshots',
      test: imageSnapshot({ storybookUrl: 'http://my-specific-domain.com:9010' }),
    });

    The above config will use https://my-specific-domain.com:9010 for screenshots. You can also use query parameters in your URL (e.g. for setting a different background for your storyshots, if you use @storybook/addon-backgrounds).

    You may also use a local static build of storybook if you do not want to run the webpack dev-server:

    import initStoryshots from '@storybook/addon-storyshots';
    import { imageSnapshot } from 'addon-storyshots-wdio';
     
    initStoryshots({
      suite: 'Image storyshots',
      test: imageSnapshot({ storybookUrl: 'file:///path/to/my/storybook-static' }),
    });

    Specifying options to jest-image-snapshots

    If you wish to customize jest-image-snapshot, then you can provide a getMatchOptions parameter that should return the options config object. Additionally, you can provide beforeScreenshot which is called before the screenshot is captured.

    import initStoryshots from '@storybook/addon-storyshots';
    import { imageSnapshot } from 'addon-storyshots-wdio';
    const getMatchOptions = ({ context: { kind, story }, url }) => {
      return {
        failureThreshold: 0.2,
        failureThresholdType: 'percent',
      };
    };
    const beforeScreenshot = (page, { context: { kind, story }, url }) => {
      return new Promise(resolve =>
        setTimeout(() => {
          resolve();
        }, 600)
      );
    };
    initStoryshots({
      suite: 'Image storyshots',
      test: imageSnapshot({ storybookUrl: 'http://localhost:6006', getMatchOptions, beforeScreenshot }),
    });

    getMatchOptions receives an object: { context: {kind, story}, url}. kind is the kind of the story and the story its name. url is the URL the browser will use to screenshot.

    beforeScreenshot receives the WebdriverIO browser instance and an object: { context: {kind, story}, url}. kind is the kind of the story and the story its name. url is the URL the browser will use to screenshot. beforeScreenshot is part of the promise chain and is called after the browser navigation is completed but before the screenshot is taken. It allows for triggering events on the page elements and delaying the screenshot and can be used avoid regressions due to mounting animations.

    Specifying custom browser options (WebdriverIO)

    You might want to use different options for the instance of browser object.

    import initStoryshots from '@storybook/addon-storyshots';
    import { imageSnapshot } from 'addon-storyshots-wdio';
     
    const browserOptions = {
      logLevel: 'error',
      path: '/', // remove `path` if you decided using something different from driver binaries.
      capabilities: {
        browserName: 'firefox'
      }
    }
     
    initStoryshots({
      suite: 'Image storyshots',
      test: imageSnapshot({ storybookUrl: 'http://localhost:6006', browserOptions }),
    });

    Specifying a custom WebdriverIO browser instance (WebdriverIO)

    You might use the async getCustomBrowser function to obtain a custom instance of a WebdriverIO browser object. This will prevent storyshots-wdio from creating its own browser.

    import initStoryshots from '@storybook/addon-storyshots';
    import { imageSnapshot } from 'addon-storyshots-wdio';
     
    (async function() {
        initStoryshots({
          suite: 'Image storyshots',
          test: imageSnapshot({
            storybookUrl: 'http://localhost:6006',
            getCustomBrowser: () => remote({
              logLevel: 'trace',
              capabilities: {
                  browserName: 'chrome'
              }
            }),
          })
        });
    })();

    Specifying a custom after test function

    You might need a function which is executed after image comparison and has access to test result, browser object and current image to attach it to some kind of report or something similar. For that you might use afterTest function. afterTest receives and object { failed, browser, image, context, url } which can be used for a custom action after test.

    import initStoryshots from '@storybook/addon-storyshots';
    import { imageSnapshot } from 'addon-storyshots-wdio';
     
    (async function() {
        initStoryshots({
          suite: 'Image storyshots',
          test: imageSnapshot({
            storybookUrl: 'http://localhost:6006',
            afterTest: ({ failed, image, context: { id } }) => {
              if (failed) {
                fs.writeFile(getCurrentSnapshot(`${id}.png`), Buffer.from(image, 'base64'));
              }
            ),
          })
        });
    })();

    Integrate image storyshots with regular app

    You may want to use another Jest project to run your image snapshots as they require more resources: Chrome and Storybook built/served. You can find a working example of this in the official-storybook example.

    Integrate image storyshots with Create React App

    You have two options here, you can either:

    • Simply add the storyshots configuration inside any of your test.js file. You must ensure you have either a running storybook or a static build available.

    • Create a custom test file using Jest outside of the CRA scope:

      A more robust approach would be to separate existing test files ran by create-react-app (anything (test|spec).js suffixed files) from the test files to run storyshots with image snapshots. This use case can be achieved by using a custom name for the test file, ie something like image-storyshots.runner.js. This file will contains the initStoryshots call with image snapshots configuration. Then you will create a separate script entry in your package.json, for instance

      {
        "scripts": {
          "image-snapshots": "jest image-storyshots.runner.js --config path/to/custom/jest.config.json"
        }
      }

      Note that you will certainly need a custom config file for Jest as you run it outside of the CRA scope and thus you do not have the built-in config.

      Once that's setup, you can run yarn image-snapshots.

    Example

    A fully running example can be seen in storyshots.test.js

    Reminder

    An image snapshot is simply a screenshot taken by a web browser.

    The browser opens a page (either using the static build of storybook or a running instance of Storybook)

    If you run your test without either the static build or a running instance, this wont work.

    To make sure your screenshots are taken from latest changes of your Storybook, you must keep your static build or running Storybook up-to-date. This can be achieved by adding a step before running the test ie: yarn build-storybook && yarn image-snapshots. If you run the image snapshots against a running Storybook in dev mode, you don't have to worry about the snapshots being up-to-date because the dev-server is watching changes and rebuilds automatically.

    Install

    npm i addon-storyshots-wdio

    DownloadsWeekly Downloads

    4

    Version

    5.3.10

    License

    MIT

    Unpacked Size

    16.6 kB

    Total Files

    9

    Last publish

    Collaborators

    • andrcuns