I got tired of downloading Playwright artifacts from CI, so I changed the workflow

I got tired of downloading Playwright artifacts from CI — so I changed the workflow Debugging Playwright failures in CI has always felt more manual than it should be. Not because the data isn’t there — it is. But because it’s scattered. A typical failure for me looks like this: open CI job download artifacts open trace viewer locally check screenshots scroll logs try to line everything up It works… but it’s slow. Especially when multiple tests fail at once. The real problem The issue isn’t lack of data. It’s that there’s no single place to understand what happened. Everything lives in separate files: traces screenshots logs CI output So debugging turns into stitching together context manually. It gets worse with: parallel runs flaky tests multiple failures triggered by the same root cause At that point you’re not debugging — you’re reconstructing events. What I tried instead I wanted to answer one simple question faster: “What actually happened in this run?” So I changed the workflow.