How to Automate Screenshot Testing in Your CI/CD Pipeline (Without Puppeteer Headaches)

Puppeteer was supposed to make browser automation easy. And for local dev, it often is. But the moment you push it to CI/CD, things get messy fast. Here's what a typical Puppeteer setup looks like in a GitHub Actions workflow: - name : Install Chrome dependencies run : | sudo apt-get install -y libnss3 libatk1.0-0 libatk-bridge2.0-0 libcups2 libdrm2 libxkbcommon0 libxcomposite1 libxdamage1 libxfixes3 libxrandr2 libgbm1 libasound2 - name : Run screenshot tests run : node screenshot-tests.js env : PUPPETEER_SKIP_CHROMIUM_DOWNLOAD : false And that's before you hit the real problems: Chrome crashes with "Error: Protocol error (Target.createTarget): Target closed" Memory leaks on long test runs that OOM-kill your runner Flaky timeouts because CI machines are slower than your laptop Different Chrome versions across environments causing visual diffs The Root Problem Puppeteer in CI means you're running a full browser as a side effect of your build pipeline. That browser needs: A specific Chro