site-verify

End-to-end user journey verification checks full-stack flows for 404s, console errors, network failures, and database state mismatches. By using Chrome DevTools MCP, you can capture snapshots and inspect network traffic to validate backend state against expectations after each step.

Yes, end-to-end QA automation for site verification requires Docker-based services and Chrome DevTools MCP connectivity. These dependencies are necessary to run reproducible, reportable checks against a running backend and perform MCP-driven network debugging.

To inspect network traffic and console errors during full-stack development, use Chrome DevTools MCP to capture snapshots and list console messages. This allows you to monitor public and authenticated pages, surfacing issues for quick remediation during multi-step journeys.

Automating backend validation for authenticated pages is best achieved through MCP-driven checks run against a running backend. This approach validates complete user journeys, ensuring backend state matches expectations and catching network failures reproducibly.

Yes, you can use site verification commands for multi-step journeys in QA scenarios. The prescribed verification commands apply to development and QA scenarios, enabling you to walk through defined user journey steps and validate data-driven pages.

End-to-end site verification fails to catch console errors without MCP connectivity because Chrome DevTools MCP provides the required observability. It powers the capture of snapshots and the listing of console messages needed to surface issues during full-stack flows.