As you build more complex UIs like pages, components become responsible for more than just rendering the UI. They fetch data and manage state. Interaction tests allow you to verify these functional aspects of UIs.
In a nutshell, you start by supplying the appropriate props for the initial state of a component. Then simulate user behavior such as clicks and form entries. Finally, check whether the UI and component state update correctly.
In Storybook, this familiar workflow happens in your browser. That makes it easier to debug failures because you're running tests in the same environment as you develop components: the browser.
You start by writing a story to set up the component's initial state. Then simulate user behavior using the play function. Finally, use the test-runner to confirm that the component renders correctly and that your interaction tests with the play function pass. Additionally, you can automate test execution via the command line or in your CI environment.
playfunction is a small snippet of code that runs after a story finishes rendering. You can use this to test user workflows.
- The test is written using Storybook-instrumented versions of Jest and Testing Library.
@storybook/addon-interactionsvisualizes the test in Storybook and provides a playback interface for convenient browser-based debugging.
@storybook/test-runneris a standalone utility—powered by Jest and Playwright—that executes all of your interactions tests and catches broken stories.
To enable interaction testing with Storybook, you'll need to take additional steps to set it up properly. We recommend you go through the test runner documentation before proceeding with the rest of the required configuration.
Run the following command to install the interactions addon and related dependencies.
Update your Storybook configuration (in
.storybook/main.js|ts) to include the interactions addon.
The test itself is defined inside a
play function connected to a story. Here's an example of how to set up an interaction test with Storybook and the
Once the story loads in the UI, it simulates the user's behavior and verifies the underlying logic.
Below is an abridged API for user-event. For more, check out the official user-event docs.
|Selects the text inside inputs, or textareas and deletes it
|Clicks the element, calling a click() function
|Clicks the element twice
|Removes the selection from a specific option of a select element
|Hovers an element
|Simulates the keyboard events
|Selects the specified option, or options of a select element
|Writes text inside inputs, or textareas
userEvent.type(await within(canvasElement).getByRole('my-input'),'Some text');
|Unhovers out of element
For complex flows, it can be worthwhile to group sets of related interactions together using the
step function. This allows you to provide a custom label that describes a set of interactions:
This will show your interactions nested in a collapsible group:
If you check your interactions panel, you'll see the step-by-step flow. It also offers a handy set of UI controls to pause, resume, rewind, and step through each interaction.
play function is executed after the story is rendered. If there’s an error, it’ll be shown in the interaction addon panel to help with debugging.
Since Storybook is a webapp, anyone with the URL can reproduce the error with the same detailed information without any additional environment configuration or tooling required.
Streamline interaction testing further by automatically publishing Storybook in pull requests. That gives teams a universal reference point to test and debug stories.
Storybook only runs the interaction test when you're viewing a story. Therefore, you'd have to go through each story to run all your checks. As your Storybook grows, it becomes unrealistic to review each change manually. Storybook test-runner automates the process by running all tests for you. To execute the test-runner, open a new terminal window and run the following command:
If you need, you can provide additional flags to the test-runner. Read the documentation to learn more.
Once you're ready to push your code into a pull request, you'll want to automatically run all your checks using a Continuous Integration (CI) service before merging it. Read our documentation for a detailed guide on setting up a CI environment to run tests.
If you're writing interaction tests with TypeScript, you may run into a situation where the TypeScript types aren't recognized in your IDE. This a known issue with newer package managers (e.g., pnpm, Yarn) and how they hoist dependencies. If you're working with Yarn the process happens automatically and the types should be recognized. However, if you're working with pnpm, you'll need to create a
.npmrc file in the root of your project and add the following:
If you're still encountering issues, you can always add the
@types/testing-library__jest-dom package to your project.
Interaction tests can be expensive to maintain when applied wholesale to every component. We recommend combining them with other methods like visual testing for comprehensive coverage with less maintenance work.
Interaction tests integrate Jest and Testing Library into Storybook. The biggest benefit is the ability to view the component you're testing in a real browser. That helps you debug visually, instead of getting a dump of the (fake) DOM in the command line or hitting the limitations of how JSDOM mocks browser functionality. It's also more convenient to keep stories and tests together in one file than having them spread across files.
- Test runner to automate test execution
- Visual tests for appearance
- Accessibility tests for accessibility
- Interaction tests for user behavior simulation
- Coverage tests for measuring code coverage
- Snapshot tests for rendering errors and warnings
- End-to-end tests for simulating real user scenarios
- Unit tests for functionality