Why Use Applitools
Find Bugs Earlier
Using Storybook and visual UI testing detects component bugs way 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.
Almost As Fast as Unit Testing
Our Storybook SDKs use Applitools Ultrafast Grid, so you can test hundreds of UI components in less than a minute. That helps you stay in the flow and keep on coding.
Our Ultrafast Grid supports multiple types of browsers, so you can find bugs that don’t appear on Chrome, but do on Firefox. That means fewer embarrassing cross-browser bugs.
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. We let you test on a wide range of viewport sizes; so you can find bugs responsive design bugs.
Want to learn more about component testing? We’ve got you covered!
At first our developers didn’t believe in visual automation. Now they’ve been singing Applitools’ praises because it catches critical bugs.Greg Sypolt • GannettDirector, Quality Engineering
How Applitools Works with Storybook
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 Ultrafast Grid.
Our ultrafast 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.