Visual Testing
Approve changes
Accept intentional visual changes and update baselines.
When a visual change is intentional — a redesigned component, updated content, new feature — you approve it. Approving a change updates the baseline so future tests compare against the new appearance.
Approving individual scenarios
In the Diff Viewer, click the Approve button on a specific scenario. This:
- Copies the test screenshot to replace the baseline
- Marks the scenario as approved for this run
- Future tests compare against the new baseline
Approving all changes
From the Tests tab, you can Approve All failing scenarios in a run. This bulk-approves every visual difference in that run.
Review each change carefully before using Approve All. Once approved, the old baselines are overwritten.
When to approve vs. when to fix
| Scenario | Action |
|---|---|
| You redesigned the hero section | Approve — the change is intentional |
| A button shifted 2px due to a CSS bug | Fix — debug and re-run |
| A third-party widget changed appearance | Approve or add a content rule |
| Font rendering differs slightly | Increase the threshold |
Approval notifications
When scenarios are approved, configured integrations are notified with the scenario.approved event. This is useful for tracking approvals in Slack or through webhooks.