How visual regression testing works

UI Verify runs as a single step in your CI. You hand it a built Storybook or a Playwright archive; it does the rest in the cloud and reports back on the pull request. Here is what happens between the upload and the check.

1. Your CI runs uiverify upload with your built Storybook or Playwright archive.
2. UI Verify ingests the build and resolves the baseline for each story from its branch history.
3. A fleet of workers renders every story in a real browser and diffs it against its baseline.
4. An AI judge reviews each changed story and labels it a likely regression or a likely intended change, with a reason.
5. A check and a comment land on your PR, with the changes grouped and pre-sorted for review.

Baselines are per branch. A change stays a change until a human, or an agent you authorized, accepts it - and accepting is what sets the new baseline. Nothing updates itself behind your back, which is what keeps a green build trustworthy. See Baselines and branches.

Everything after the upload happens in the cloud. There are no browsers to install in CI, no snapshot images committed to your repo, and no local render farm to babysit. Your pipeline stays one step.