nebula-visual-verification

Focused visual testing targets specific changed component routes and named mock states across desktop, tablet, and mobile viewports. You run a browser-side helper to collect deterministic contrast, overflow, and image signals before declaring a pass, avoiding noisy exploratory checks.

Visual QA should collect deterministic contrast ratios, overflow metrics, and image context as machine-readable evidence. Capturing these signals across desktop, tablet, and mobile viewports for each named mock state reliably detects obvious image and copy regressions.

Yes, automated visual verification runs a browser-side helper for each target component route, mock state, and viewport combination. This deterministic approach captures contrast, overflow, and image signals across desktop, tablet, and mobile without manual exploratory inspection.

Visual verification works by targeting specific Workbench preview routes and authored named mock states. It scopes checks to these defined states across multiple viewports, ensuring deterministic signal collection rather than unfocused full-app testing.

Handle failures using a guided remediation loop with auto-fix and reverify capabilities. A checklist-driven pass/fail rubric evaluates collected contrast, overflow, and image signals, with explicit stuck and closeout rules producing concise deterministic outcomes with artifacts only when needed.

Visual verification requires running the browser helper because it captures deterministic contrast, overflow, and image signals as machine-readable evidence. Without these collected signals across all target states and viewports, a reliable pass declaration cannot be made.