browser-verification

Browser verification automates UI verification in real browsers using Playwright to detect visual regressions and runtime errors after code changes. It performs visual checks, interaction testing, and console error detection to prevent CSS and layout issues before code review.

Browser verification is an automated process that validates UI changes in real browsers to catch visual regressions and runtime JavaScript errors. It uses Playwright to execute visual checks and interaction tests, ensuring layout and component integrity before production.

Yes, browser verification requires a dev server or an accessible rendering environment to operate. Playwright automates the browser against this running environment to validate UI components and detect runtime errors during the workflow.

You trigger browser verification by executing the work flow step in the work pipeline after making UI changes. This integrated step automatically leverages Playwright to validate layouts, components, and interactions across real browsers.

Yes, browser verification detects runtime JavaScript errors and CSS issues by performing visual checks and console error detection. It leverages Playwright to automate interactions and catch layout regressions in the rendered output.

Browser verification is limited to detecting visual regressions, runtime JavaScript errors, and CSS issues within an accessible dev server environment. It operates within the work workflow and requires a running rendering environment to execute Playwright checks.