Flaky test detection
Mark recurring visual changes as ignored, or let Snapvisor auto-ignore changes that keep reappearing across builds, so flaky screenshots stop demanding review.
Some screenshots wobble for reasons that aren't real regressions — an animation frame, a timestamp, a random avatar. Snapvisor lets you stop those from demanding review every time.
Ignoring changes manually
Turn on ignore changes in a project's settings and reviewers can mark a recurring or flaky change as ignored. Ignored changes no longer require review on future builds. Turning the setting off means new builds ignore nothing again; builds that already ran are unaffected.
Auto-ignoring flaky changes
With ignore enabled you can also let Snapvisor auto-ignore changes that keep reappearing. A change is treated as flaky once it shows up at least a configured number of times across auto-approved builds within a rolling 7-day window.
The threshold is a minimum occurrence count — the default is 3. Raise it to be stricter about what counts as flaky, lower it to catch noise sooner.
Keeping signal high
Auto-ignore is scoped to auto-approved builds, so it learns from branches you already trust rather than from unreviewed pull requests. Combine it with monitoring mode so your trusted branches feed the flaky-change history.