Developer says Works On My Machine but Playright Disagrees (QA Humor)

"Works on my machine" is the developer's oldest escape hatch, and this is how a QA engineer shuts it down for good using Claude and Playwright. If you've ever handed over a bug report with steps, logs, and a screen recording only to get four smug words back, this one's for you. It's software testing reality as a comedy sketch, with a real technique underneath. I walk through how I kill the "works on my machine" argument before it starts: I have Claude write a Playwright test that reproduces the bug, then run it cross-browser on a clean CI machine with no cache. Chromium, Firefox, WebKit, mobile viewport. When it fails across every browser, there's nothing left to argue about. I wrote up the full breakdown over on QA Revolution, including the exact cross-browser Playwright config and the Claude prompt I use to turn a bug report into a working reproduction test. Link below. Here's what we get into: Why "works on my machine" is an environment problem, not a bug problem Using Claude to turn a bug report into a real Playwright test Cross-browser testing across Chromium, Firefox, WebKit, and mobile Reading the Playwright trace viewer to prove a failure frame by frame Running tests on a clean CI runner so cache and local state can't lie for you Tools mentioned in this video: Claude — claude.com Playwright — playwright.dev Serious question for the comments: what's the most ridiculous "works on my machine" moment a developer has ever hit you with? I'm collecting the best ones for a future episode in this series. Subscribe for more QA and AI testing content that's equal parts real technique and therapy for testers. #softwaretesting #qahumor #developerlife #playwright #techhumor