web-validation

Automate browser health checks by running validation workflows against a running dev server to detect runtime issues, capture multi-viewport screenshots, and validate console and network activity.

Visual regression testing detects UI changes by capturing screenshots at 375px, 768px, and 1920px viewports, allowing you to compare current output against baseline evidence to identify CSS or layout regressions across devices.

Yes, you need a browser automation engine like Playwright MCP or Chrome DevTools MCP to execute automated checks, interact with the DOM, and collect runtime evidence from the web application.

Yes, automated browser validation integrates into CI checks to alert on failing routes, hydration issues, or CSS regressions by capturing screenshots, console logs, and network traces into an evidence directory.

The best way to collect e2e evidence is to configure an evidence directory where the validation workflow automatically stores screenshots, console logs, and network traces captured during browser-based health checks.

Validate forms and monitor network activity by running browser automation against a running dev server to detect runtime issues, verify form submissions, and capture network traces for performance and error analysis.