HN Showcase
Back to browse
GitHub Repository

Playwright CI reporter — aggregates failures across parallel jobs into a single debuggable view. 5,000+ downloads.

9 starsTypeScript

Open-source Playwright reporter for debugging CI failures

by sentinelqa·Mar 17, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●MidShip ItNiche Gem

Playwright's built-in HTML reporter already aggregates traces, screenshots, and videos.

Strengths
  • •withSentinel wrapper preserves existing reporter configuration without breaking current setups.
  • •Local mode works without accounts or tokens for teams avoiding cloud dependencies.
  • •Sets sensible artifact defaults for trace, screenshot, and video retention on failures.
Weaknesses
  • •Playwright's native HTML reporter already shows traces, screenshots, and videos together.
  • •Cloud mode pushes toward Sentinel SaaS product rather than staying fully open-source.
Target Audience

QA engineers and developers running Playwright tests in CI pipelines

Similar To

Playwright HTML Reporter · Allure · ReportPortal

Post Description

Playwright generates excellent debugging artifacts (traces, screenshots, videos, logs), but when tests fail in CI those artifacts are often scattered across logs and storage.

In practice this means debugging a failure usually involves downloading multiple files and trying to reconstruct what happened.

I built an open-source Playwright reporter that aggregates all artifacts from a test run into a single report.

It works locally and in CI using the artifacts Playwright already produces.

The goal is to make it faster to understand why a test failed without digging through CI outputs.

Would love feedback from teams using Playwright at scale.

GitHub: https://github.com/adnangradascevic/playwright-reporter

Similar Projects

Developer Tools●●Solid

Ratunit – A TUI for browsing JUnit XML test reports written in Rust

The repo sensibly separates concerns — a standalone junit-parser crate plus a ratatui-based viewer — which makes reuse straightforward. The UI shows sensible affordances (file tabs, suite list, failure detail with stack traces and vim-like keybindings) and even ships via Homebrew and cargo, but it’s a focused niche tool rather than something disruptive — missing things I’d expect next are search/filtering and CI/web integration.

Niche GemCozySolve My Problem
pure-orange
113mo ago