comparing-branches-visually

To compare UI changes visually, set up two independent git worktrees for your base and feature branches, run dev servers on separate ports, capture synchronized screenshots, and generate a before/after visual diff report.

A visual diff report is a concise output mapping changed routes to their before/after visuals, generated by capturing synchronized screenshots from two development environments running on different ports.

You can run two development servers on different ports by setting up independent git worktrees for your branches, launching each server on a separate port like 3000 and 3001, and navigating to changed routes to capture screenshots.

Yes, you need two independent worktrees to verify visual regressions, as this allows you to run separate development servers on different ports simultaneously to capture synchronized before/after screenshots for comparison.

The best way to validate UI parity is to generate synchronized visual diffs by running two dev servers on separate ports for your base and feature branches, then producing a concise visual diff report of changed routes.