The proof pack for every test run
An open pack format that captures what was tested, exactly what happened, and whether every promise held. Use any test runner. Open the pack anywhere.
The problem
Everyone ships proof.
Nobody can open it.
Every runner invents its own artifact. The reader you need is always the one you don't have.
Playwright-report/index.html
needs a web server, and the folder beside it copy both or the report breaks
playwright-report/index.html
a schema only mochawesome understands — useless to any other reporting tool
junit.xml
pass or fail, and nothing else at all — no timing, no page, no reason why
The solution
Evidence Viewer
No upload. No account. Opens offline. Just download a sample pack, drop it in the viewer
Input
Preview
Or load a sample run
Playwright Evidence
ReportInstancesIssuesCoverage1go to https://ltqa-domsetu.vercel.app/ switch to nested iframe and complete the checkout flow
Passedkane-cli recorded 2 weeks ago100%
Pass Rate
4m 41s
Duration
1 Passed0 FailedFlaky
❄️ 0
Always Failing
⚠️ —
New Failures
⚠️ —
Anomalies
📈 —
Chain of custody
Produced
the runner wrote each step
as it happened
Sealed
finalize hashed it, sha256
tamper-evident
Carried
one file: Slack, S3, a stick
no server involved
Opened
read back offline, byte for byte
human · agent · auditor
$ kane-cli run "verify checkout flow on staging"
• 12 steps • 3 assertions • passed in 41s
→ pack sealed: run-2f9a1.evi
Kane CLI ships it by default
Every Kane CLI run already ends in an evidence pack.
If you want the full loop, start there.
An open format, not a lock-in
Evidence is a documented, open spec. Build your own writer or reader on top of it.
Read SpecsSPEC.md · .evidence v1
├ manifest.json ├ verdicts/ ├ trajectory/ | ├ steps.ndjson | └ screenshots/ └ checksum.sha256
