- For those without a play function: it verifies whether the story renders without any errors.
- For those with a play function: it also checks for errors in the play function and that all assertions passed.
The test-runner is a standalone, framework-agnostic utility that runs parallel to your Storybook. You will need to take some additional steps to set it up properly. Detailed below is our recommendation to configure and execute it.
Run the following command to install it and the required dependencies.
package.json scripts and enable the test runner.
Start your Storybook with:
Finally, open a new terminal window and run the test-runner with:
Test runner offers zero-config support for Storybook. However, you can run
test-storybook --eject for more fine-grained control. It generates a
test-runner-jest.config.js file at the root of your project, which you can modify. Additionally, you can extend the generated configuration file and provide testEnvironmentOptions as the test runner also uses jest-playwright under the hood.
The test-runner is powered by Jest and accepts a subset of its CLI options (for example,
If you're already using any of those flags in your project, you should be able to migrate them into Storybook's test-runner without any issues. Listed below are all the available flags and examples of using them.
|Output usage information |
|Run in stories json mode. Automatically detected (requires a compatible Storybook) |
|Disables stories json mode |
|Directory where to load Storybook configurations from |
|Run in watch mode |
|Define the URL to run tests in. Useful for custom Storybook URLs |
|Define browsers to run tests in. One or multiple of: chromium, firefox, webkit |
|Specifies the maximum number of workers the worker-pool will spawn for running tests |
|Disable the cache |
|Deletes the Jest cache directory and then exits without running tests |
|Display individual test results with the test suite hierarchy |
|Use this flag to re-record every snapshot that fails during this test run |
|Creates a local configuration file to override defaults of the test-runner |
By default, the test-runner assumes that you're running it against a locally served Storybook on port
6006. If you want to define a target URL to run against deployed Storybooks, you can use the
--url flag or set the
TARGET_URL environment variable. For example:
You can also configure the test-runner to run tests on a CI environment. Documented below are some recipes to help you get started.
If you're publishing your Storybook with services such as Vercel or Netlify, they emit a
deployment_status event in GitHub Actions. You can use it and set the
deployment_status.target_url as the
TARGET_URL environment variable. Here's how:
💡 The published Storybook must be publicly available for this example to work. We recommend running the test server using the recipe below if it requires authentication.
You can use your CI provider (for example, GitHub Actions, GitLab Pipelines, CircleCI) to build and run the test runner against your built Storybook. Here's a recipe that relies on third-party libraries, that is to say, concurrently, http-server, and wait-on to build Storybook and run tests with the test-runner.
💡 By default Storybook outputs the build to the
storybook-static directory. If you're using a different build directory, you'll need to adjust the recipe accordingly.
The test-runner is a generic testing tool that can run locally or on CI and be configured or extended to run all kinds of tests.
Chromatic is a cloud-based service that runs visual and interaction tests (and soon accessibility tests) without setting up the test runner. It also syncs with your git provider and manages access control for private projects.
However, you might want to pair the test runner and Chromatic in some cases.
- Use it locally and Chromatic on your CI.
- Use Chromatic for visual and interaction tests and run other custom tests using the test runner.
The test-runner renders a story and executes its play function if one exists. However, certain behaviors are impossible to achieve via the play function, which executes in the browser. For example, if you want the test-runner to take visual snapshots for you, this is possible via Playwright/Jest but must be executed in Node.
The test-runner exports test hooks that can be overridden globally to enable use cases like visual or DOM snapshots. These hooks give you access to the test lifecycle before and after the story is rendered. Listed below are the available hooks and an overview of how to use them.
|Executes once before all the tests run|
|Executes before a story is rendered|
|Executes after the story is rendered|
💡 These test hooks are experimental and may be subject to breaking changes. We encourage you to test as much as possible within the story's play function.
To enable the hooks API, you'll need to add a new configuration file inside your Storybook directory and set them up as follows:
💡 Except for the
setup function, all other functions run asynchronously. Both
postRender functions include two additional arguments, a Playwright page and a context object which contains the
title, and the
name of the story.
When the test-runner executes, your existing tests will go through the following lifecycle:
setupfunction is executed before all the tests run.
- The context object is generated containing the required information.
- Playwright navigates to the story's page.
preRenderfunction is executed.
- The story is rendered, and any existing
playfunctions are executed.
postRenderfunction is executed.
The test-runner transforms your story files into tests when testing a local Storybook. For a remote Storybook, it uses the Storybook's stories.json file (a static index of all the stories) to run the tests.
Suppose you run into a situation where the local and remote Storybooks appear out of sync, or you might not even have access to the code. In that case, the
stories.json file is guaranteed to be the most accurate representation of the deployed Storybook you are testing. To test a local Storybook using this feature, use the
--stories-json flag as follows:
stories.json mode is not compatible with watch mode.
If you need to disable it, use the
Stories.json mode requires a
stories.json file. Open a browser window and navigate to your deployed Storybook instance (for example,
https://your-storybook-url-here.com/stories.json). You should see a JSON file that starts with a
"v": 3 key, immediately followed by another key called "stories", which contains a map of story IDs to JSON objects. If that is the case, your Storybook supports stories.json mode.
If your tests time out with the following message:
It might be that Playwright couldn't handle testing the number of stories you have in your project. Perhaps you have a large number of stories, or your CI environment has a really low RAM configuration. In such cases, you should limit the number of workers that run in parallel by adjusting your command as follows:
By default, the test runner truncates error outputs at 1000 characters, and you can check the full output directly in Storybook in the browser. However, if you want to change that limit, you can do so by setting the
DEBUG_PRINT_LIMIT environment variable to a number of your choosing, for example,
DEBUG_PRINT_LIMIT=5000 yarn test-storybook.
As the test runner is based on Playwright, you might need to use specific docker images or other configurations depending on your CI setup. In that case, you can refer to the Playwright CI docs for more information.