Skip to content
Visual-diff manual

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.

The behaviour worth knowing is what happens at the edges. A set held by a registered worktree cannot be deleted, and the console says what holds it rather than failing quietly. Choosing two sets to compare fills the job form for you, and the tab you are on is part of the address, so a comparison you set up survives a reload and a link.

The visual-diff console in sample mode: a panel of three screenshot sets listing branch, date and story count, a compare picker beneath them, and a job form on the right explaining that a deployed instance cannot start a job.The visual-diff console in sample mode: a panel of three screenshot sets listing branch, date and story count, a compare picker beneath them, and a job form on the right explaining that a deployed instance cannot start a job.
The console, deployed. The sample badge is the subject of its own page; the sets panel and the compare picker are what the scenarios below describe.
Before each task
  • the console has screenshot sets

The console lists the screenshot sets

  1. When I visit the console
  2. Then I see each screenshot set with its branch, story count and size
  3. And a set captured from a dirty tree is marked as dirty

Comparing two sets pre-fills the job form

  1. When I visit the console
  2. And I choose two sets to compare
  3. Then the job form is set to compare those two sets

Deleting a held screenshot set is refused with the reason

  1. Given a screenshot set is held by a registered worktree
  2. When I delete the held set
  3. Then the deletion is refused naming what holds it

The console names the next capture set for me

  1. When I visit the console
  2. And I ask the console to name the capture set
  3. Then the label field holds a set label no screenshot set already uses

The selected job tab is a link

  1. When I visit the console
  2. And I switch to the compare job tab
  3. Then the URL carries the compare job mode
  4. When I reload the console
  5. Then the compare job tab is selected

Asking for the same comparison again lands, from another tab

  1. When I visit the console
  2. And I choose two sets to compare
  3. And I switch to the capture job tab
  4. Then the URL has dropped the compare job mode
  5. When I choose the same two sets to compare
  6. Then the job form is set to compare those two sets

Past runs are listed with their outcome

  1. When I visit the console
  2. Then the history lists each run with its outcome, exit code and duration