Skip to content

kane-qe: a card in the chat for every test Claude runs, use-case detail, History, remote suites - #1

Merged
4DvAnCeBoY merged 11 commits into
LambdaTest:mainfrom
lt-zeeshan:feat/remote-usecase-history
Oct 10, 2026
Merged

4DvAnCeBoY merged 11 commits into
LambdaTest:mainfrom
lt-zeeshan:feat/remote-usecase-history

Conversation

@lt-zeeshan

Copy link
Copy Markdown
Collaborator

What this adds

A card in the chat. A kane-cli test Claude runs (run, testmd run, testrun run) is drawn in the conversation in place of its shell row:

  • one line while it runs, behind a spinner: name, time, current step;
  • then a bordered card with the mascot: the result, a failure's on / why / kind, or a suite's cells, counts and up to three failures;
  • View steps opens the pane on that run; View evidence opens the run's evidence pack in kane-cli's viewer in one click;
  • where the chat is printed text (terminal outside fullscreen) the card ends with the evidence path instead of buttons;
  • a command that never became a run keeps its normal row.

Use-case detail. Press a use case on the Assurance tab: title, risk, what it owes to design and to run, kane-cli's reason and next command, and Close these gaps with Claude.

History tab. The last 30 finished runs in the project (it was 10, shown only as last run …). /kane history opens it.

Remote suites. testrun run --remote: the band says how many tests are on the grid and since when, and the pane gives the job and its link, instead of sitting on "planning".

A spinner leads the running step on the band and the card, and the mascot's eyes step every 120 ms.

Found in live takes, and fixed

  • Saved tests that match a change equally are ordered by last result (failed first, then most recent), not by folder order.
  • A run started outside the chat is named from its own process's command line (ps), so a test file shows its file name.
  • The idle band counts each test once, by its latest result: a failure that has since passed is gone.
  • Use-case cards show their title; a reason shared by every row is said once.
  • A long test name in the offer card is cut to its width instead of wrapping under the button.

One thing to decide

View evidence starts kane-cli evidence serve <pack> and opens the link it prints. That is the one kane-cli command the mod now starts besides cover gaps; it still never starts a test. It also reads that one printed line, because the viewer has no structured output. With no pack or no viewer it falls back to asking Claude, as before. If the "mod never starts anything" rule should stay absolute, this is the part to change.

How it was checked

  • claude plugin test kane-qe: 127 pass (81 before). claude plugin validate passes for the plugin and the marketplace.
  • Live: a real Claude Code session in a fullscreen terminal, a demo shop project with a real requirement store, and real kane-cli runs. guide/run_tour_v3.sh records that session; guide/make_promo.py cuts a captioned promo from a take.
  • Not checked live: remote suites (written from kane-cli's docs/remote-execution.md, tests only); the browser tab opening after View evidence (the viewer start was seen, the tab was not recorded); the card's evidence-path form outside fullscreen; the desktop app.

guide/v2/design-coverage.md has the detail. The version is left at 2.0.0 for whoever releases.

🤖 Generated with Claude Code

lt-zeeshan and others added 11 commits October 9, 2026 23:17
Remote suites: a suite sent to the grid reports its tests only when the
job ends, so the band sat on "planning". It now reads remote_start,
remote_dispatched and remote_error: the band shows how many tests are on
the grid and since when, the pane names the grid, the job and its link,
and a job that fails before any test reports gives every test its reason.

Use-case detail: a use case on the Assurance tab opens to its title,
risk and what it still owes to design and to run, each with kane-cli's
reason and next command. "Close these gaps with Claude" hands that to
Claude; the mod still runs nothing itself.

History: a third tab lists the finished runs kept for the project (30,
up from 10), with when, how long, and where each failed or a suite's
counts. /kane history opens it. Older stored entries still read.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
One step of the loop every 150 ms, down from 260.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A test Claude runs (run, testmd run, testrun run) is drawn in the
conversation in place of its shell row: one line while it runs, then a
bordered card with the mascot, the result, a failure's on/why/kind or a
suite's cells, counts and up to three failures. View steps opens the
pane on that run.

View evidence opens the run's sealed pack in kane-cli's local viewer in
one click: the mod starts `kane-cli evidence serve <pack>`, reads the
viewer link it prints and opens it. This is the one kane-cli command the
mod starts besides `cover gaps`; it still never starts a test. With no
pack or no viewer, Claude is asked instead. The pane's Open evidence
button does the same.

Where the chat is printed text (the terminal outside fullscreen) the
card ends with the evidence path instead of buttons. A command that
never became a run keeps its normal row. A folded group of shell calls
is unfolded when it holds a run, so the card shows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Found in a live session against a real requirement store: the list showed
only uc-1, and the detail repeated one reason and one command per row.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Saved tests that match a change equally: the one that last failed comes
  first, then the one run most recently, then by name (it was the order
  the folder listed them in).
- The offer card cuts a long test name to its width instead of wrapping it
  under the button.
- A run nobody started in this chat is named from its own process's
  command line, so a test file started in a terminal shows its file name.
- The chat card keeps the failing step to one line: a designed test's
  step can run to a paragraph.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A test that failed and then passed counted as one of each, and its old
failure stayed on row 2. Found in a live take: after Claude fixed the bug
and the test passed, the band still named the failure.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On the band's row 2 and on the chat card's running line the step read as
a plain sentence. A one-cell spinner now leads it, stepping with the
mascot: repainted in place on a terminal, a glyph elsewhere.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
run_tour_v3.sh drives a real Claude Code session with the plugin through
the chat card, the fix and its test, auto mode, a suite, outside runs,
assurance with a use case, and History. make_promo.py cuts captioned
clips from a take, with per-clip crops and masks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@4DvAnCeBoY
4DvAnCeBoY merged commit 7d54354 into LambdaTest:main Oct 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants