Snapshot tests compare the rendered markup of every story against known baselines. It’s a way to identify markup changes that trigger rendering errors and warnings.
Storybook is a helpful tool for snapshot testing because every story is essentially a test specification. Any time you write or update a story, you get a snapshot test for free.
Run the following command to install Storyshots:
Add a test file to your environment with the following contents to configure Storyshots:
Run your first test. Storyshots will recognize your stories (based on .storybook/main.js's setup) and save them in the snapshots directory.
When you make changes to your components or stories, rerun the test to identify the changes to the rendered markup.
If they're intentional, accept them as new baselines. If the changes are bugs, fix the underlying code, then rerun the snapshot tests.
Next, update your test file (e.g.,
storybook.test.js) to the following:
When you run your tests, the snapshots will be available in the directory you've specified.
By default, Storyshots detects your project's framework. If you run into a situation where this is not the case, you can adjust the configuration object and specify your framework. For example, if you wanted to configure the addon for a Vue 3 project:
These are the frameworks currently supported by Storyshots:
Storyshots is highly customizable and includes options for various advanced use cases. You can read more in the addon’s documentation.
Visual tests capture images of stories and compare them against image baselines. Snapshot tests take DOM snapshots and compare them against DOM baselines. Visual tests are better suited for verifying appearance. Snapshot tests are useful for smoke testing and ensuring the DOM doesn’t change.