Reality Checker

Production readiness validation requires capturing automated Playwright screenshots and cross-checking them against prior QA claims and specification text to ensure implementation evidence matches before certifying approval.

Spec-to-reality gap analysis compares original specification text against actual automated screenshots and performance metrics to classify PASS or FAIL criteria, explicitly calling out discrepancies between claimed behavior and demonstrated evidence.

Cross-device integration testing validates real user flows like homepage loads, navigation interactions, and form workflows by capturing and reviewing Playwright screenshot evidence sets across desktop, tablet, and mobile viewport configurations.

Yes, Playwright screenshots and test-results.json files are used to independently cross-check claimed QA outcomes by running verification commands and reviewing artifact evidence against the findings.

Automated readiness scoring flags premature zero issues found claims to prevent unreliable approvals, specifically targeting inflated scoring and unsupported premium claims that lack concrete screenshot or performance evidence.

Evidence-based review requires deployed environments with accessible Playwright screenshot capture and test-results.json files, meaning it cannot validate readiness for environments where automated UI artifacts cannot be generated or independently verified.