Storybook and visual testing: Why testing isolated components is not enough
Storybook has become the standard for documenting and testing UI components. But for visual testing, testing isolated components is not enough.
Read more →4 articles
Storybook has established itself as the reference environment for developing, documenting and testing isolated UI components. For teams maintaining a design system, every story becomes a natural target for visual testing: a component rendered in a precise state, with no application dependency, perfectly reproducible. This fine granularity makes it possible to detect a visual regression at the button or card level, before it ever propagates into an assembled page.
The articles on this page cover the Storybook ecosystem through the lens of visual testing: integration with Chromatic (the native tool from the Storybook team), alternatives like Loki, Storyshots or Playwright component testing, handling of decorators and states (hover, focus, dark mode), best practices to make stories deterministic. We also tackle the recurring question: should you only test components in stories, or also the real pages that assemble them? The two approaches are complementary, and that is precisely where Delta-QA fits in — testing web pages rendered under real conditions, complementing component coverage provided by Storybook. This page helps structure a coherent strategy across both levels.
Storybook has become the standard for documenting and testing UI components. But for visual testing, testing isolated components is not enough.
Read more →Lost Pixel (npm, config-based) vs Delta-QA (no-code, accessible to non-developers). Complete comparison of both approaches.
Read more →Chromatic (Storybook components) vs Delta-QA (full pages, no-code). Compare: components vs pages, complementarity, and use cases.
Read more →Storybook visual testing without Chromatic: compare Percy, Playwright & Delta-QA. No-code reviews, no credit card, no lock-in, no per-snapshot bill.
Read more →