Skip to main content
Each Kane CLI run produces an evidence pack: one sealed .evidence file that holds everything you need to understand the run, from the test definition to the screenshots, logs, and failure details of every step. The pack is a self-contained zip file. You can open it in the hosted viewer, share it with a teammate, archive it in CI, validate it, or merge several packs into one.

​
What’s inside a pack

Whether you open a pack in the viewer or unzip it, you find:
  • The test definition: what was asked of the agent.
  • A result summary: status, duration, per-step outcomes, tags, who ran it (user name/email), a share link, and the environment (browser resolution, OS version).
  • Per-step screenshots: the page as the agent saw it, plus an annotated copy highlighting the element the agent acted on.
  • Browser console and network logs: captured for the whole run and attributed to the step that produced them.
  • Run logs: the CLI and runner logs for the execution.
  • Failure records: on failed runs, a per-step record with the error message, the page state at failure, and references into the console/network logs.
Mobile runs add two things. The result summary records the device in the run environment, such as the device model and OS version. The per-step logs also include device logs from the emulator or simulator, next to the usual browser logs.
Run artifacts live only in the pack. Kane CLI does not keep a separate log directory for each run on disk.

​
Where packs live

Every run except testrun run seals its pack in the session directory:
Runs you keep are also copied into the project store, a folder in your working directory:
Whether a pack is copied to the project store depends on how you ran the test: An interactive TUI session produces one pack. The pack collects every run in the session and is sealed when you /exit or start over with /new. If Kane CLI crashes during a run, it removes incomplete or orphaned packs automatically the next time it starts. Packs that belong to other Kane CLI processes still running are left alone. You never need to clean up by hand.

​
The kane-cli evidence commands

​
Publishing to the dashboard

When a run uploads to Test Manager, its sealed pack is attached automatically. Replayed testmd runs and testrun executions also publish their packs to your project. The dashboard therefore shows execution evidence even for runs that replay from cache, where the agent does not author the steps again.

​
Next steps