Prompt
I'm unhappy with Chromatic because baseline updates are tedious
Latest observation
That’s a common pain point with visual regression tools.
If the main issue is that baseline updates are too tedious, you probably want a workflow that makes “approve the new normal” cheaper and less manual. A few options:
If you want to stay with Chromatic
Try to reduce baseline churn by:
- Grouping approvals: review multiple related changes together instead of one-by-one.
- Tightening stories/tests: fewer noisy snapshots means fewer baseline updates.
- Using ignore regions / masking for dynamic content like dates, ads, avatars, or timestamps.
- Stabilizing rendering: fix fonts, animations, data loading, and viewport inconsistency.
- Setting stricter CI rules so only meaningful diffs reach the review stage.
If you want to switch tools/workflow
You might prefer a system that supports:
- Local review and approval before pushing baselines
- Git-based baseline storage so updates are just code changes
- Easier bulk accept/reject
- Less screenshot noise or more deterministic rendering
Alternatives people often consider:
- Percy
- Playwright + screenshot assertions
- Loki
- Argos
- Applitools if you want more advanced visual AI, though it can still have its own workflow overhead
A potentially simpler approach
If your team mostly wants to catch accidental UI changes, you may not need a heavy visual platform. A Playwright screenshot test suite in Git can be much simpler operationally:
- baselines live in the repo
- updates happen through normal PRs
- review is done in the same code review flow
That said, it depends on your scale and how much flakiness you’re seeing.
If you want, I can help you compare Chromatic vs Playwright screenshots vs Percy specifically for “baseline update friction,” or suggest a workflow that minimizes manual approval.