Introducing Kinora: a Playwright test dashboard with history, flaky tracking, and traces

Description and use

Kinora aggregates Playwright CI reports, stores history, surfaces flaky tests, and embeds trace viewers, streamlining team debugging.

Problem

Teams need to analyze Playwright test results across many CI runs to identify new failures, flaky tests, and trace failures without downloading artifacts.

Outcome

Kinora provides a persistent, searchable view of Playwright test history, enabling faster triage of failures, identification of flaky tests, and inline trace inspection without artifact downloads.

Workflow

• Add Kinora reporter to Playwright config or upload results.json via CLI
• Run Playwright in CI as usual
• Kinora normalizes the report and uploads the run through a REST API
• Dashboard stores run data, tests, metadata, and trace artifacts
• Team accesses Kinora to review current or historical runs

Evidence

Playwright gives you an excellent HTML report for a single test run. You can open a failed test, inspect screenshots, read errors, and launch the trace viewer when you need the full story.

Source

Teams usually fill that gap with a mix of CI artifacts, screenshots, Slack messages, local downloads, and tribal knowledge.

Source

Kinora keeps the run data in one place so you can see: run history by project, pass rate trends, failed and flaky tests, retries and durations, git and CI metadata, trace.zip artifacts attached to failures.

Source

The important part is stable test identity. Kinora derives a cross‑run key from the test file, title path, and project name.

Source

Kinora keeps the trace attached to the failed test. From the dashboard, you can open it directly in the embedded trace viewer without downloading the zip or switching tools.

Source