Flakiness ranked
Tests that flip between pass and fail across runs are surfaced and ranked, not buried inside a single run's retries.
[ Flaky tests ]
A flaky test dashboard for Playwright
kinora is a flaky test dashboard for Playwright: it watches every run and surfaces the tests that pass and fail without code changes, so you can find, rank, and fix them instead of hitting retry.
Flaky tests hide in per-run retries: the report goes green, the flake is invisible, and trust in the suite erodes. kinora compares each test's outcome across your entire run history, so tests that flip between pass and fail are surfaced and ranked, with the full timeline and the trace one click away.
kinora.dev/tests
Flaky or broken
A test that fails and keeps failing since a commit is broken, not flaky. kinora tells the two apart, says why, and names the commit where the breakage started.
No retries needed
Playwright only reports a flake when a retry passes. kinora also reads it from the history: the same commit passing and failing, or a test that keeps flipping.
History behind every flake
See the full pass/fail timeline for a test to judge how bad a flake really is before you spend time on it.
Straight to the trace
One click from a flaky failure to its full Playwright trace, embedded inline.
Alerts on regressions
Get notified in Slack, email, or webhook the moment a stable test starts failing.
FAQ
How does kinora detect flaky tests?
It reads the last 20 runs of each test. A test is flaky when it passed and failed on the same commit, needed a retry to pass, or flipped between pass and fail at least 3 times. One bad run between two good ones is not enough: that is often a regression the next commit fixed.
What is the difference between a flaky and a broken test?
A flaky test passes and fails on the same code: stabilize it or quarantine it. A broken test fails and keeps failing because a change broke it: fix it. kinora flags each test as one or the other and links a broken test to the run and commit where it started failing.
Can I get alerted about new flaky tests?
Yes. Per-project alerts fire on new failures and regressions, delivered via Slack, email, or webhook.
Do I need to change my tests to use it?
No. Send results with @kinora/reporter or the CLI and flaky detection is automatic; there are no test-code changes.
Awaiting first signal
Push your first run.
Add the reporter, point it at a kinora server, and watch the history build itself.