Interact with your Storybook and get test code generated for you. To see this live, check out the demo.
First, install the package.
npm install --save-dev storybook-addon-test-codegen
This addon requires storybook
version >=8.3.0
to be installed in your project. Ensure you have a compatible version
by running:
npm install --save-dev storybook@latest
If you’re not using Storybook already, you can refer to the Storybook Getting Started Guide for installation instructions.
For storybook@8.2.*
, use version 1.0.3
of this addon.
Once installed, register it as an addon in .storybook/main.js
.
// .storybook/main.ts
// Replace your-framework with the framework you are using (e.g., react-webpack5, vue3-vite)
import type {StorybookConfig} from '@storybook/your-framework';
const config: StorybookConfig = {
// ...rest of config
addons: [
'@storybook/addon-essentials',
'storybook-addon-test-codegen', // 👈 register the addon here
],
};
export default config;
Enable recording in the Interaction Recorder tab in the Storybook UI. Interact with your components as you normally
would, and the addon will generate test code for you. Click "Add assertion" to add assertions like
expect().toBeVisible()
to the generated code.
Click on "Save to story" to save the generated code to the story file. Done 🎉
Alternatively, copy both imports and the generated code to your test file like so:
// MyComponent.stories.tsx
// 👇 Add the generated imports here
import {userEvent, waitFor, within, expect} from "@storybook/test";
export const MyComponent = {
// ...rest of the story
// 👇 Add the generated test code here
play: async ({canvasElement}) => {
const canvas = within(canvasElement.ownerDocument.body);
await userEvent.click(await canvas.findByRole('textbox', {name: 'Name'}));
await userEvent.type(await canvas.findByRole('textbox', {name: 'Name'}), 'John Doe');
}
}
The addon helps you write better tests by showing warnings when it detects potential improvements in your selectors. It highlights cases where:
- Roles are used without names (which can make tests fragile)
- Query selectors are used (which can break when HTML structure changes)
- Test IDs are used (which don't reflect how users interact with your app)
For each warning, you'll get suggestions on how to improve your selectors to make tests more reliable and maintainable.
This addon contributes the following parameters to Storybook, under the testCodegen
namespace:
Type: string
The attribute to use for generating findByTestId
queries. Defaults to 'data-testid'
.
Example:
{
parameters: {
testCodegen: {
testIdAttribute: 'data-test-id'
}
}
}
Any contributions are welcome. Feel free to open an issue or a pull request.