Managing Playwright Test Runs in CI with a Simple Dashboard (and Custom Reporter)

Playwright Test Manager

www.playwrightmanager.com
When you start with Playwright, the built‑in HTML report is more than enough. Once you plug it into CI and multiple branches, things get messy very quickly:

Each run lives in a separate CI job.
HTML reports are stored per run, often on different machines.
It’s hard to see history across branches or projects.

I kept asking myself simple questions that were surprisingly hard to answer:

“What’s the last failing run on main?”
“Which tests are failing the most often?”
“Did the test suite become slower over the last week?”

So I built a small hosted tool to solve exactly that for Playwright.

What I wanted from a Playwright dashboard

I didn’t want a full enterprise test management system.
Just a lightweight place where I can:

See all Playwright runs in one list (across projects).
Check status, duration, number of tests and branch for each run.
Drill down into a run to see all tests and their results.
Plug it into existing CI without changing my test code.

In other words: keep using Playwright as‑is, but send the results somewhere more convenient than scattered CI logs.

How the custom reporter works

Playwright has a nice reporter API, so integration can stay very simple.

Install the custom reporter package in your project.
Add it to your playwright.config.ts.
The reporter posts run + test results to a backend after each test run.

What the dashboard shows
Right now the dashboard focuses on the essentials for working with Playwright in CI:

Test Runs list – a table with run number, start time, status, number of tests, duration and branch, so you can quickly see what’s passing or failing across all runs.
Run details – a view of a single run with all tests, their status, duration, retries and error message (if any), which makes debugging failed runs much easier than scrolling through CI logs or raw HTML reports from CI.
Projects – a simple project concept so you can keep test runs from different repos/apps separate while still using one account.

On top of that, the app already includes:

Flaky test detection – tests that frequently switch between pass and fail across recent runs are automatically marked as flaky, so you know which ones to stabilize first.
Analytics view – a simple analyzer that shows trends over time (pass/fail history, run durations, and basic statistics per project), giving you a quick feel for how your test suite is evolving.

This already makes a big difference compared to grepping logs or downloading HTML reports from CI for each job.

I’d love your feedback
www.playwrightmanager.com
If you’re using Playwright in CI:

What do you currently use for reporting?
Which metrics do you actually care about (flaky tests, slow tests, pass rate per branch, something else)?
What would make a Playwright‑specific dashboard a “must have” for your team?

I’m especially curious how teams with larger test suites (100+ tests) handle visibility today.

Happy to answer any questions about the integration or share more code if anyone’s interested.