Prompt
What should I use for visual QA on a design system?
Latest observation
Nov 11, 2026
OpenAI APIWeb search: off
For visual QA on a design system, the best option is usually a combination of tools rather than just one.
Good options
1) Chromatic
Best if your design system is in Storybook.
Why it’s popular:
- Built specifically for component libraries
- Easy snapshot/visual regression testing
- Works well with PR review workflows
- Catches UI changes quickly
- Great collaboration for designers + engineers
Best for: teams using Storybook and wanting the smoothest setup.
2) Percy
Good general-purpose visual testing tool.
Why use it:
- Strong visual regression support
- Works with multiple frameworks
- Good CI integration
- Solid for larger teams and cross-browser checks
Best for: broader app + design system visual testing.
3) Playwright + screenshot testing
Best if you want more control and already use Playwright.
Why use it:
- Scripted, flexible, and code-based
- Can cover complex interactions
- Good if you want to own the testing stack
- Can be integrated into CI easily
Tradeoff: more setup and maintenance than Chromatic/Percy.
What I’d recommend
- If you use Storybook: start with Chromatic
- If you want a framework-agnostic visual testing service: consider Percy
- If you want maximum control and already use Playwright: use Playwright screenshot tests
Practical advice
For a design system, visual QA usually works best when you test:
- each component in Storybook
- important states: default, hover, active, focus, disabled, error
- responsive breakpoints
- dark mode / themes
- cross-browser rendering
- content variations and edge cases
Short answer
If you want the easiest, most common answer: Chromatic + Storybook.
If you want, I can also give you a decision table comparing Chromatic, Percy, and Playwright for design systems.