The real trace viewer
The same Playwright trace viewer you know, timeline, DOM snapshots, network, and console, running inside the dashboard.
[ Trace viewer ]
kinora embeds the full Playwright trace viewer in the browser, so any failure, live or from run history, opens inline. No downloading trace.zip, no local playwright show-trace.
Debugging a CI failure usually means downloading a trace.zip and running the trace viewer locally. kinora hosts the trace and embeds the real Playwright trace viewer in the dashboard, so a red test is one click from its full timeline, DOM snapshots, network, and console, right in the browser.
The same Playwright trace viewer you know, timeline, DOM snapshots, network, and console, running inside the dashboard.
Click a failure and the trace opens inline. No fetching trace.zip and running show-trace on your machine.
Open the trace for any past run, not just the latest, because kinora keeps them.
Prefer local? The kinora desktop app is a standalone Playwright trace viewer that needs no account.
Yes. kinora hosts the trace and embeds the Playwright trace viewer in the browser, so it opens inline on any failure with no download step.
Yes. The trace viewer is vendored from Playwright, so the timeline, snapshots, network, and console tabs behave exactly as you expect.
Yes, with the kinora desktop app, a standalone local Playwright trace viewer that needs no account.
Add the reporter, point it at a kinora server, and watch the history build itself.