Piwi DashboardSelf-hosted Playwright observability

A permanent home for your test results — live streaming, failure clustering, AI diagnosis, cross-run analytics, and team triage. No external services required.

Getting started

Live demo

GitHub

📊

Test results storage

Store complete Playwright test run data — status, duration, retries, errors, and more — in a lightweight SQLite database.

🎯

Project organization

Tests are organized by project. Unknown projects are automatically created when results are submitted via API.

📈

Performance tracking

Step-level timing, avg/P90 duration trends, slowest-tests analysis, and side-by-side run comparison.

🌐

Network request analysis

Find slow API endpoints grouped by HTTP method and normalized route (e.g. `/api/users/:id`).

📖

Interactive API docs

Auto-generated OpenAPI 3.1 specification with a Scalar-powered reference UI at /docs — browse endpoints, schemas, and execute requests directly from the browser.

🔬

Browser Web Vitals

Capture TTFB, DOMContentLoaded, FCP and more via the Performance API, displayed with color-coded thresholds.

🔌

Playwright reporter

Drop-in custom reporter that automatically uploads results, HTML reports, and trace files after each run.

🔐

Authentication

Optional role-based access control with administrator, reporter, and user roles.

☁️

Flexible storage

Local file storage by default, or S3-compatible storage (AWS S3, MinIO, DigitalOcean Spaces, Cloudflare R2).

🐳

Docker support

Pre-built multi-platform container images (~200 MB) available on GitHub Container Registry.

See it in action

Dashboard overview — stats and test results trend chart

Dashboard overview — at-a-glance stats and a test results trend chart across all projects

Projects list — last-run status, duration, and test pass/fail ratio for every project

Project detail — complete run history with status badges and test breakdown

Performance — avg/P90 duration trend, slowest tests ranking, and side-by-side run comparison

Test run detail — every test case with status, duration, location, and error messages

Failure clusters — tests sharing the same root cause are grouped by error fingerprint

Flaky tests — composite flakiness score with retry-pass and alternation detection

Cluster triage — set status, write triage notes, and track resolution