visual_test

Visual regression testing captures baseline and current screenshots of a UI feature across fixed breakpoints, then diffs them to detect layout and styling changes. It flags regressions by categorized severity to prevent unnoticed UI breakages.

To perform visual regression testing on a terminal UI, capture baseline and current terminal output at fixed sizes like 80x24 and 120x40. The Skill then diffs these captures to detect layout and styling changes in your TUI workflows.

Yes, visual regression testing works with Chrome MCP to capture GUI screenshots at fixed breakpoints like 320, 768, 1024, and 1440px. It validates responsive reflow, alignment, overflow, and touch target sizing across these states.

Visual regression testing includes accessibility checks that validate WCAG contrast ratios, focus indicator visibility, screen-reader landmark structure, and keyboard-only navigation completeness alongside standard screenshot diff comparisons.

Screenshot diffing requires deterministic capture parameters across fixed breakpoints and terminal sizes to function correctly. Without structured storage of baseline and current assets, the generated report cannot accurately flag regressions or validate layout results.

The best way to automate UI behavior validation is to capture screenshots at fixed breakpoints like 320/768/1024/1440px, compute pixel differences, and generate a report that classifies regressions by severity from CRITICAL to INFO.