Watch a video tutorial on the Storybook channel
Play functions are small snippets of code executed after the story renders. Enabling you to interact with your components and test scenarios that otherwise required user intervention.
We recommend installing Storybook's
addon-interactions before you start writing stories with the
play function. It's the perfect complement for it, including a handy set of UI controls to allow you command over the execution flow. At any time, you can pause, resume, rewind, and step through each interaction. Also providing you with an easy-to-use debugger for potential issues.
Run the following command to install the addon and the required dependencies.
Update your Storybook configuration (in
.storybook/main.js) to include the interactions addon.
play functions are small code snippets that run once the story finishes rendering. Aided by the
addon-interactions, it allows you to build component interactions and test scenarios that were impossible without user intervention. For example, if you were working on a registration form and wanted to validate it, you could write the following story with the
💡 See the Interaction testing documentation for an overview of the available API events.
When Storybook finishes rendering the story, it executes the steps defined within the
play function, interacting with the component and filling the form's information. All of this without the need for user intervention. If you check your
Interactions panel, you'll see the step-by-step flow.
Thanks to the Component Story Format, an ES6 module based file format, you can also combine your
play functions, similar to other existing Storybook features (e.g., args). For example, if you wanted to verify a specific workflow for your component, you could write the following stories:
By combining the stories, you're recreating the entire component workflow and can spot potential issues while reducing the boilerplate code you need to write.
Most modern UIs are built focusing on interaction (e.g., clicking a button, selecting options, ticking checkboxes), providing rich experiences to the end-user. With the
play function, you can incorporate the same level of interaction into your stories.
A common type of component interaction is a button click. If you need to reproduce it in your story, you can define your story's
play function as the following:
When Storybook loads the story and the function executes, it interacts with the component and triggers the button click, similar to what a user would do.
Asides from click events, you can also script additional events with the
play function. For example, if your component includes a select with various options, you can write the following story and test each scenario:
In addition to events, you can also create interactions with the
play function based on other types of asynchronous methods. For instance, let's assume that you're working with a component with validation logic implemented (e.g., email validation, password strength). In that case, you can introduce delays within your
play function to emulate user interaction and assert if the values provided are valid or not:
When Storybook loads the story, it interacts with the component, filling in its inputs and triggering any validation logic defined.
You can also use the
play function to verify the existence of an element based on a specific interaction. For instance, if you're working on a component and want to check what happens if a user introduces the wrong information. In that case, you could write the following story:
If you need, you can also adjust your
play function to find elements based on queries (e.g., role, text content). For example:
When Storybook loads the story, the
play function starts its execution and queries the DOM tree expecting the element to be available when the story renders. In case there's a failure in your test, you'll be able to verify its root cause quickly.
Otherwise, if the component is not immediately available, for instance, due to a previous step defined inside your
play function or some asynchronous behavior, you can adjust your story and wait for the change to the DOM tree to happen before querying the element. For example:
By default, each interaction you write inside your
play function will be executed starting from the top-level element of the Canvas. This is acceptable for smaller components (e.g., buttons, checkboxes, text inputs), but can be inefficient for complex components (e.g., forms, pages), or for multiple stories. To accommodate this, you can adjust your interactions to start execution from the component's root. For example:
Applying these changes to your stories can provide a performance boost and improved error handling with