Using KwikQA
Failure report
The failure report is one HTML file, kwikqa-report.html, that shows an analysis to anyone: a reviewer, a lead, or whoever reads the CI run. Writing one is free on every plan and needs no sign-in.
Write one
$ npx kwikqa analyze --html # analyze, then write the report
$ npx kwikqa report # the latest analysis's report, sending nothing
$ npx kwikqa analyze --local --html # no account, nothing sent
--output <path>writes it somewhere else.kwikqa report --run <id>picks an earlier run under.kwikqa/runs/.- In CI,
kwikqa ciwrites it on every run, and the KwikQA Action keeps it as an artifact.
What it shows
- The run's counts: tests, failed, flaky, passed, and skipped.
- Each failure group, numbered as
analyzenumbered it, which is the numberfix --grouptakes. Each group shows its tests, its owner (test code, application, or environment), the diagnosis, and the evidence the diagnosis cites. - Flaky tests, and failures no rule could classify.
- What KwikQA could see for each evidence channel, such as the report, traces, the DOM, the network, and source, and what it left out and why.
- Every request that was sent, with its model and its token use.
- The repair that followed the analysis, if any.
A local analysis (--local) gets the same report without owners or diagnoses.
How report rebuilds it
Run records keep no evidence, so kwikqa report rebuilds it from the same test report and artifacts the analysis read. If they have changed since the analysis, the report says so rather than show evidence the diagnosis didn't see.
Sharing it
- Self-contained. The file loads nothing from the network. It stays readable when a viewer blocks its script and styles, as Jenkins does for archived HTML by default.
- Redacted. It holds the same redacted evidence a request preview shows, so share it the way you share CI logs.
- Safe to overwrite. KwikQA only ever replaces a file it wrote itself, and
initoffers to addkwikqa-report.htmlto.gitignore.