Using Storybook and visual UI testing detects component bugs far upstream in the development process, when you first code your components. This prevents bugs from appearing downstream in applications, when they’re harder to diagnose.
Our Storybook SDKs use our Visual Grid, so you can test hundreds of UI components in less than a minute. That means no interruption to your development workflow.
Our Visual Grid supports multiple types of browsers, so you can find bugs that don’t appear on Chrome, but do on Firefox.
You’ve got plenty of code to write as it is. With Applitools, you don’t write any code to test React, Vue, and Angular components built with Storybook. Just a couple of commands and you’ve run your first visual test.
Your customers use your app across all kinds of devices: phones, tablets, laptops, and more. Each with its own browser size that can affect UI component rendering. Applitools lets you test on a wide range of viewport sizes, so you can find bugs due to responsive design.
You run an npx command, as detailed in this tutorial. Our Storybook SDK then extracts all stories from your Storybook, and renders each component across all visual states. For each rendering, our Storybook SDK then extracts a DOM Snapshot that we send to Applitools Visual Grid. Our visual grid renders the component across multiple browsers with different viewport sizes, in parallel. Each component rendering screenshot is sent to our AI comparison engine to find significant differences that indicate a visual bug.