Visual-diff manual

The visual-diff console captures a screenshot of every component in this repository, compares one capture against another, and shows what moved — this is its manual.

Start here

The console is deployed and runs on committed sample data — nothing you click there can start a job or delete anything.

Take the five-step tour Open the console

Visual-diff console

The console is the front door. It lists the screenshot sets captured so far — each with the branch it came from, how many stories it holds and how large it is — and it starts the jobs that produce and compare them.

7 scenarios

Visual-diff report

A report is the record of one comparison run: every variant judged against its counterpart, sorted into buckets, with the screenshots behind each verdict. It opens on a summary — a count for every bucket, and both capture sets named above the results.

15 scenarios

Sample mode

A deployed console has no data directory to read, so it serves a committed set of fixtures instead, and says so. Every screen fed from those fixtures carries a badge.

4 scenarios

About this manual

Every page here is built from the acceptance scenarios that decide whether a change may merge. They are not a description of the console written alongside it — they are the requirements themselves, rendered. A scenario cannot change without this manual changing in the same commit.

That fixes the genre, so it is worth stating plainly: the pages above are a behavioural reference with some task framing, not a promised how-to. The console is a local tool with one operator, and the instance linked at the top of this page runs on committed sample data. If you are here to judge the mechanism rather than to operate the tool, those pages are written for you.