Skip to content

kane-cli 0.10.7

Latest

Choose a tag to compare

@lt-user-access-token-stage lt-user-access-token-stage released this 20 Nov 10:50
· 4 commits to main since this release
9853ef1

Highlights

This release adds first-class bug tracking to the CLI — mark the bugs a test hits, manage your org's RCA categories, and have the next root-cause analysis read them back. Explorations can now be named at creation, Windows testrun --remote works against the grid, and custom headers travel with every test run.

[0.10.7] - 2026-11-20

Bug tracking that feeds back into analysis

  • Mark the bugs a test hits — the new kane-cli bugs commands record known bugs against a test, and the next RCA run reads them instead of starting from scratch.
  • Your org's own RCA categories — kane-cli bugs categories lists the available root-cause categories and lets you add and manage the ones specific to your organization.
  • Known bugs and categories show up in results — the known bug ID and the org category name are carried through to failure.yaml, so triage output matches what you recorded.
  • Take back feedback the same way you gave it — kane-cli bugs retire now makes it clear that feedback can be withdrawn regardless of how it was submitted.

Named explorations

  • Name an exploration when you start it — kane-cli explore run --name <name> labels the exploration it creates, and the name follows through to the export so runs are easy to find later.
  • Retries keep their identity — retrying an exploration without passing a name no longer loses track of it.

Remote runs on Windows

  • testrun --remote works from Windows — kane-cli starts HyperExecute and sends the grid POSIX-style paths, so remote runs no longer break on Windows path separators.

Requests go out the way you configured them

  • Custom headers are sent on test runs — headers configured for a test are now included in kane-cli test runs.
  • Header problems never kill a run — a bad or unusable custom header is handled gracefully instead of failing the whole run.

More trustworthy TLS and clearer replay evidence

  • Corporate and self-signed certificates work everywhere — background worker threads now use the same OS certificate store trust as the main thread, so runs behind a proxy or custom CA behave consistently.
  • Assertion details survive into triage — passed assertions carry their checks into the evidence, and failed assertions carry both the expected and observed values into the verdict.

Install

# npm
npm install -g @testmuai/kane-cli@0.10.7

# Homebrew
brew install lambdatest/kane/kane-cli

# Shell installer (latest release)
curl -fsSL https://raw.githubusercontent.com/LambdaTest/kane-cli/main/install.sh | bash

Compare: 0.10.6...0.10.7