Playwright Test Failures Can't Distinguish App Bugs from Stale Tests — Here's a Fix

Failing Playwright end-to-end tests produce the same red error whether an app has regressed or a test has simply gone out of date, leaving developers to manually investigate the cause. A developer frustrated with this ambiguity built a system where each UI element is represented as a named, typed control object carrying its selector, human-readable label, and action type. This approach auto-generates structured, machine-readable logs of exactly which UI controls a test touched during a run, without requiring manually written or maintained description strings. Because both the test failure log and a pull request diff share CSS selectors as a common key, an automated system can check whether the PR actually modified the element that caused the failure. The intersection of these two datasets allows CI to flag whether a test failure is likely caused by an intentional product change or a genuine regression, without human investigation.