agency-reality-checker

You can prevent premature production approvals by enforcing evidence-based integration verification that requires automated Playwright screenshots, test-results.json metrics, and cross-validated QA artifacts before certifying readiness.

Evidence-based integration verification is a process that validates complete user flows using automated captures and test metrics, defaulting to a NEEDS WORK status unless overwhelming visual and QA proof is provided.

You can enforce screenshot evidence and test metrics by requiring automated Playwright captures and test-results.json files as mandatory inputs, cross-validating these findings against QA reports before allowing any deployment.

Yes, you can use Playwright screenshots to validate end-to-end user journeys by capturing before and after images of navigation, forms, and interactions, then matching them with performance metrics to verify production readiness.

Integration testing requires cross-validated QA artifacts to certify readiness because the verification process defaults to NEEDS WORK, demanding matched QA evidence and test-results.json metrics before any production approval.

A key limitation is that automated test results alone are insufficient for production readiness; the process strictly requires accompanying Playwright screenshots and cross-validated QA evidence to prevent fantasy approvals.