e2e-test
Use to test the Bus TUI end to end like a manual QA tester, against a QA test doc (default tests/e2e-tui/app.md, optionally only some case IDs).
Skill by asura1234
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/asura1234-e2e-test
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: documents, testing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
- Runs as
- Python package
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/e2e-test
What's inside
- Skill name
e2e-test- Description
- Use to test the Bus TUI end to end like a manual QA tester, against a QA test doc (default tests/e2e-tui/app.md, optionally only some case IDs). Builds the dev-tools variant, drives a fresh scratch Bus through `bus --dev tui` (never the running Bus), judges every step against the doc from screen text, styled cells, screenshots and recorded effects, and writes a run report with PASS/FAIL/SKIP per step and a GREEN/RED/INCOMPLETE verdict (GREEN only when every step ran and passed).
- License
- Apache-2.0
- Instructions
- 67 lines in SKILL.md · view on GitHub
Before installing
- Ships executable scripts
Files (5)
- SKILL.md
- guide.md
- e2e-run-report-format.md · references/
- e2e_report.py · scripts/
- e2e_report_test.py · scripts/tests/
SKILL.md (first lines)
# E2E Test
Read [guide.md](guide.md), [e2e-run-report-format.md](references/e2e-run-report-format.md) and
`docs/tui-driver.md` completely before driving anything. Read the whole test doc, including its
run contract, setup recipes, fixtures and decisions.
```text
INPUT = [<test doc path>] [--cases ID,ID,...]
repo = git rev-parse --show-toplevel
doc = INPUT test doc path, otherwise tests/e2e-tui/app.md
IF doc is not a file: STOP "No test doc at <doc>."
IF BUS_DATA_DIR, BUS_SESSION_ID or any HERDR_* is set in your environment
Unset them for every command below. The driver refuses to touch a live Bus anyway.
-- Build the dev variant once; ./run tui builds into its own tui-driver dir, never target/debug.
Run: ./run tui list
IF it fails: STOP with its output; the build is broken, nothing was tested.
T = the driver command: `./run tui` (each call rebuilds only if sources changed)
Every driver call for a case names its session: `T <verb> --name <name> ...`.
-- Start the report from the doc; never write case or step headings by hand.
Run:
python3 skills/e2e-test/scripts/e2e_report.py init --doc <doc> [--cases <IDs>] [--name <run folder>] \
--commit "$(git rev-parse HEAD)" --platform "<OS>, Ghostty <version> for --real, <size>"
report = its stdout line; run_dir = dirname(report)
FOR EACH case in the report, in order:
name = case ID lowercased (e.g. app-07)
Run: T start --name <name> --size <doc size, default 120x40> --run-dir <run_dir>/sessions
(add `--graphics none` only for a case the doc runs without a picture terminal; default kitty)
IF start fails: leave Session `none` and mark every step of the case FAIL, the start error as
Evidence and Seen, `none` for Trace and Screenshot; continue.
Record the start output's run_dir as the case's `Session`.
Do the case's preconditions/setup with the doc's recipes, through the UI the doc names.
Use `T bus --name <name> ...` only where the doc allows fixtures or read-only state.
IF the setup cannot be completed, or a real provider prompt appears:
mark every step of the case FAIL with what happened (fault guess per guide.md); stop the case.
FOR EACH numbered step:
Do the step's actions exactly as written (keys, clicks, typing), one driver call each.
Judge the expected result with the evidence the doc asks for (guide.md "Judging"):
text/state → snapshot, find, wait --text, wait --state, `bus state`/`history`
colours/attributes → cells, wait --style, wait --changed
visual claims → screenshot (cells) or screenshot --real (images); open the PNG
and write what you saw
opens/sounds/notifications → effects, wait --effect
Write the step's Result and Evidence into the report immediately.
IF the result does not match: FAIL with every FAIL field (format doc), a screenshot,
the session trace path and the effects; guess the fault per guide.md "Fault guess".
IF the doc allows SKIP for evidence you cannot capture: SKIP the whole step with that reason,
keeping what was captured in Evidence.
Never retry a failed step until it passes; a flaky pass is a FAIL with both runs noted.
IF a later step depends on a failed one: still attempt it; record what happened.
Run: T stop --name <name> (always, also after failures)
Run: python3 skills/e2e-test/scripts/e2e_report.py check --doc <doc> <report>
IF exit code 1: fix the report's form (never its results) and rerun check.
Append check's output under `## Summary` at the end of the report.
RETURN, verbatim: "<Verdict line> — <report path>" followed by check's per-case lines and,
for each FAIL, one line: <case> step <n>: <seen> (fault guess: <owner>).
```
Driver or skill bugs found mid-run (the driver misreads the screen, a verb fails though the UI
is fine) are `skill-driver` FAILs in the report; fixing them is separate work, after the run.From asura1234/bus, Apache-2.0.
More from asura1234/bus
- 0.592score
split-pr
asura1234
Split a multi-purpose Bus branch into single-purpose branches from an explicit base, as parallel PRs, a stacked PR train, or a mix of both, with dependencies…
SkillAFreshness: A★ 1Claude Code +9 - 0.592score
review-plan
asura1234
Iteratively and read-only review a plan file that follows the project plan template.
SkillAFreshness: A★ 1Claude Code +9 - 0.592score
review-pr
asura1234
Iterative code review in which the reviewer proves suspicions in the correctness / security / bug dimensions by writing tests that run red or, preferably for…
SkillAFreshness: A★ 1Claude Code +9 - 0.592score
address-review-comments
asura1234
Author-side adjudication and handling of plan/PR review comments, including fixed whole-file chunks with the same --scope as review-pr.
SkillAFreshness: A★ 1Claude Code +9 - 0.592score
pr
asura1234
Feature-branch PR workflow.
SkillAFreshness: A★ 1Claude Code +9 - 0.592score
delete-dead-code
asura1234
Clean up entropy on two tracks.
SkillAFreshness: A★ 1Claude Code +9 - 0.592score
gate-and-fix
asura1234
Use on a feature branch that is getting ready to commit, when lint, unit, integration, coverage, and diff gates must pass and failures must be remediated from…
SkillAFreshness: A★ 1Claude Code +9 - 0.588score
merge-pr
asura1234
Watch an open PR's two signals until it can merge — CI conclusions and review comments.
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
worktree-new
asura1234
Create a new git worktree (an isolated working copy of the repo) and provision it so it can build, test and commit out of the box — create it from a freshly…
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
commit-and-push
asura1234
Analyze the current git changes, split them into commits following "each commit does exactly one thing" with lowercase Conventional Commit subjects, and push…
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
rebase-origin-main
asura1234
Rebase the current feature branch onto the latest origin/master, triage conflicts by severity, then force-with-lease push with an explicit refspec.
SkillAFreshness: A★ 1Claude Code +9 - 0.583score
worktree-close
asura1234
Remove a git worktree that is no longer needed.
SkillAFreshness: A★ 1Claude Code +9
Signals
- Stars
- 1
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Oct 23, 2026 (6 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- Repository
- github.com/asura1234/bus
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from asura1234
- 0.592score
review-plan
asura1234
Iteratively and read-only review a plan file that follows the project plan template.
SkillAFreshness: A★ 1Claude Code +9 - 0.592score
address-review-comments
asura1234
Author-side adjudication and handling of plan/PR review comments, including fixed whole-file chunks with the same --scope as review-pr.
SkillAFreshness: A★ 1Claude Code +9 - 0.592score
pr
asura1234
Feature-branch PR workflow.
SkillAFreshness: A★ 1Claude Code +9 - 0.592score
delete-dead-code
asura1234
Clean up entropy on two tracks.
SkillAFreshness: A★ 1Claude Code +9 - 0.592score
gate-and-fix
asura1234
Use on a feature branch that is getting ready to commit, when lint, unit, integration, coverage, and diff gates must pass and failures must be remediated from…
SkillAFreshness: A★ 1Claude Code +9 - 0.592score
review-pr
asura1234
Iterative code review in which the reviewer proves suspicions in the correctness / security / bug dimensions by writing tests that run red or, preferably for…
SkillAFreshness: A★ 1Claude Code +9
Cite this page
e2e-test skill. Agent Mart. https://agentmart.dev/skills/asura1234-e2e-test (last updated 2026-10-24)