rialto-visual-diff-review

What problem does it solve?

It helps teams quickly determine whether a failing visual regression is an intentional design change, a real UI regression, or an outdated screenshot so you can act correctly without guessing.

Core Features & Use Cases

• Review the failing visual diff: Open the failing spec and inspect the light-.png versus light--diff.png outputs to understand what changed.
• Classify the change: Decide between intentional updates (new components or styling changes), regressions (broken layout or missing elements), and stale screenshots (UI changed but snapshots weren’t updated).
• Take the right next action: Either update snapshots when the change is intentional or create an issue with the relevant diff screenshot when it’s a regression.
• Prevention-focused workflow: Encourages running visual tests before claiming UI completion and adding specs for new components.

Quick Start

Run the visual test suite to reproduce the failure, inspect the generated diff PNGs, then classify the outcome as intentional vs regression vs stale and update screenshots or file an issue accordingly.