verify-tasks

You automate Playwright browser tests to check for hydration issues by triggering a verification workflow that navigates multiple pages and scenarios, using deterministic console checks to detect runtime errors. It runs against your local dev server.

The best way to verify UI consistency before deployment is to run automated browser tests across critical pages like contact forms and pricing. This workflow catches JavaScript errors and UX problems by applying deterministic checks.

Yes, you can use Playwright MCP to detect JavaScript errors on a localhost dev server. The verification process relies on a running local server at localhost:4321 and available Playwright MCP tools to execute console checks.

You run automated QA checks across multiple site pages by executing a full task session verification. It automatically navigates scenarios like contact forms, video resources, and pricing pages to ensure consistency and capture optional visual snapshots.

Yes, you need a running local server to use Playwright for automated task verification. The checks require a running dev server at localhost:4321 and available Playwright MCP tools to enable deterministic navigation and console checks.

Automated browser testing might fail to detect hydration issues if the dev server is not running at localhost:4321. The verification relies on available Playwright MCP tools to execute deterministic console checks across the specified scenarios.