Kensho — open-source test reports

検証 — verification.

Kensho is the report tool. It reads a directory of test results in the canonical Kensho v1 JSON format and emits a self-contained static HTML site you can open from any browser, host on S3, or attach to a build artifact.

Why Kensho exists

Existing OSS report tools either lock you into one ecosystem (Allure → mostly JVM/JS), don't render rich step trees, or require a server to view. Kensho is:

• Single-run, single-binary. No backend, no API key, no telemetry.
• One schema, every adapter. JS, Python, Java, Ruby, .NET, Go, k6, Postman — they all emit the same shape.
• Static, fast, accessible. Pre-compiled JSX bundles, gzipped JSON, hash routing for deep links, full keyboard navigation.
• Apache 2.0, forever.

What you get out of the box

• Suites / Behaviors / Packages tree with resizable splitter
• Real attachments — <img> previews with click-to-zoom, <video controls>, typed icons for everything else
• Step tree with HTTP request/response detail (Newman, k6, Playwright)
• Status badge SVG (kensho badge) for your README
• Single-pair diff (kensho diff prev cur) for terminal output + optional static diff site
• CODEOWNERS-aware ownership inference per test file

Where to next

• Quickstart — wire Playwright in 60 seconds
• Adapters — install snippets for every framework
• CLI reference — every flag, every command