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

说明与用途

Kinora 将 Playwright CI 报告聚合、存储历史、识别 flaky 测试，并内嵌 Trace 视图，提升团队调试效率。

问题

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

结果

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.

工作流

• 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

证据

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.

来源

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

来源

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.

来源

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

来源

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.

来源