kane-cli 0.8.4
Highlights
Remote execution on LambdaTest HyperExecute is now available via --remote, letting you run tests on the grid without leaving the CLI. The plugin system arrives with kane-cli plugin install, bringing a structured way to extend kane-cli with team-managed binaries. Local runs also get smarter consolidation: authored and replayed evidence merge into one clean, coverage-accurate execution.
[0.8.4] - 2026-08-18
Remote execution on the grid
- Run tests on LambdaTest HyperExecute with
--remote— kane-cli dispatches your test run through the backend, spawns a HyperExecute job, and streams progress back to your terminal with the job ID and a sessions path. - Automatic HyperExecute setup —
kane-cli plugin installsets up remote execution and places it where kane-cli expects it.kane-cli doctortells you whether the setup, auth, and gitignore gate are all ready before you dispatch. - Grid login now uses the right environment — remote runs pass
--envcorrectly, preventing stage credentials from being rejected against production endpoints. Chrome discovery is also handled automatically on the grid.
Plugin system
- New
kane-cli plugincommand — install, list, and remove plugins withkane-cli plugin install,kane-cli plugin list, andkane-cli plugin remove. An allowlist controls which plugins kane-cli will load. - Plugins install into a versioned local layout — installed plugins materialize bundled assets into a
cwd-local directory, so plugin versions are tied to your project rather than a global state. kane-cli doctorcovers plugin readiness — the readiness report flags a missing HyperExecute binary as an error (the plugin owns it), so you know exactly what to fix before running.
Smarter local run consolidation
- Authored and replayed evidence merge into one published execution — after a run that includes both authored and replay members, kane-cli reconciles them into a single pack with kane merge rules applied, coverage recomputed, and facts synced into the local graph.
- Author members no longer cause a preflight failure — members are now classified as
replayorauthor; author-class members run standalone with their own pack and are folded into the consolidated result at reconcile. --from-contextselects members by assurance test IDs — and automatically follows edit supersessions, so only tombstoned tests are excluded.- Gate auto-defaults now match local behavior —
project_folder_auto_defaultedsurfaces in local runs the same way it does on the grid.
A clearer terminal view
- Evidence table now works in TTY and non-TTY modes — TTY sessions get an interactive multi-pack evidence table with progress and a result box; non-TTY sessions get
servecommands for each evidence row. - Remote runs render again in the TTY view — a missing event-surface hook (
willMountTTYView) was preventing the themed progress and result box from appearing during--remoteruns. - Evidence display errors never flip the verdict — a throw in the evidence presentation layer is now isolated, so a display bug cannot change the exit code of a passing run.
- Exit codes derive from reconcile verdicts — the terminal status and exit code are now grounded in what reconcile actually decided, not an earlier assumption.
testmd improvements
testmd runaccepts--target,--device, and--app— device meta fields are carried through the evidence environment, so runs targeting specific devices report the right context.
Install
# npm
npm install -g @testmuai/kane-cli@0.8.4
# Homebrew
brew install lambdatest/kane/kane-cli
# Shell installer (latest release)
curl -fsSL https://raw.githubusercontent.com/LambdaTest/kane-cli/main/install.sh | bashCompare: 0.8.3...0.8.4