kinora vs Allure Report
Allure Report generates a portable static report per run for 50+ frameworks. kinora is a persistent, Playwright-native dashboard that keeps history across runs and embeds the Playwright trace viewer, with no CI history plumbing.
Allure Report is a great multi-language static report generator. But it's disposable: history across runs means carrying an Allure history folder between CI jobs, and persistent analytics really means the separate commercial Allure TestOps. kinora is a running dashboard: every run is stored, trends and flaky detection work out of the box, and the native Playwright trace viewer is embedded. Allure is framework-agnostic; kinora is Playwright-focused.
kinora
kinora is an open-source dashboard that ingests every Playwright run from CI and tracks pass rates, trends, and flaky tests across projects and over time, with the full Playwright trace viewer embedded inline.
Allure Report
Allure Report is an open-source, language-agnostic tool that generates a static HTML report from a single test run.
Feature by feature
| Feature | kinora | Allure Report |
|---|---|---|
| Open source | Fair source (FSL-1.1); MIT client libs | Apache-2.0 |
| Frameworks | Playwright, Vitest (browser mode), Storybook | 50+ languages / frameworks |
| Persistent cross-run history | Built in | Manual history folder |
| Trends & analytics dashboard | In-report trends; persistent dashboard needs TestOps | |
| Flaky detection | Across run history | Per-run categorization |
| Embedded Playwright trace viewer | ||
| Runs as a server / live dashboard | No (static HTML) | |
| Alerts on regressions | ||
| PR comment on CI runs (GitHub, GitLab) | ||
| MCP server for coding agents | Allure TestOps (paid) | |
| Hosted cloud option | kinora cloud (free tier + paid) | Allure TestOps (separate paid) |
| Self-host | Docker Compose | Static files, host anywhere |
Which should you pick?
Choose kinora when
- You're Playwright-first and want a live dashboard with real cross-run history and trends.
- You want flaky tracking, regression alerts, and the embedded Playwright trace viewer.
- You don't want to stitch history together in CI or buy Allure TestOps.
- Your coding agent (Claude Code, Cursor, any MCP client) pulls failing tests, traces, and flaky history from CI over MCP.
Choose Allure Report when
- You test across many languages and frameworks, not just Playwright.
- You want a portable static report you can archive and open anywhere.
- You don't want to run a server at all.
FAQ
Is kinora an alternative to Allure Report?
For Playwright teams, yes. Allure Report generates a static per-run report across many frameworks; kinora is a persistent Playwright-native dashboard with cross-run history and the embedded trace viewer.
Does Allure Report keep history across runs?
Not on its own. You carry an Allure history folder between CI runs, and full persistence is Allure TestOps, a separate commercial product. kinora stores every run automatically.
Does kinora support non-Playwright frameworks?
No. kinora is Playwright-focused. If you need many languages or frameworks, Allure is the broader tool.
Push your first run.
Add the reporter, point it at a kinora server, and watch the history build itself.