42 lines
1.6 KiB
Markdown
42 lines
1.6 KiB
Markdown
---
|
|
id: 1177d1f5-6df7-42ae-beef-bbd6b22d2fae
|
|
type: workflow
|
|
title: "Workflow: TUI testing with mcp-tui-driver in Claude Code"
|
|
tags: [mcp, tui-testing, documentation, claude-home, workflow, development]
|
|
importance: 0.6
|
|
confidence: 0.8
|
|
created: "2026-03-02T00:38:21.757641+00:00"
|
|
updated: "2026-03-02T00:38:21.757641+00:00"
|
|
---
|
|
|
|
# TUI Testing Workflow with mcp-tui-driver
|
|
|
|
## Context
|
|
|
|
Documentation added to `development/tui-testing.md` in the claude-home repo. Context loading trigger added to `CLAUDE.md`.
|
|
|
|
## Context Loading Trigger
|
|
|
|
Keywords: `tui testing`, `mcp-tui-driver`, `tui automation`, `terminal ui test`
|
|
Loads: `development/tui-testing.md`
|
|
|
|
## Typical Testing Workflow
|
|
|
|
1. **Launch** — `tui_launch` to start the TUI app in a managed session
|
|
2. **Wait** — `tui_wait_for_idle` or `tui_wait_for_text` until app is ready
|
|
3. **Inspect** — `tui_snapshot` (accessibility tree) or `tui_text` (raw text) to read state
|
|
4. **Interact** — `tui_press_key`, `tui_send_text`, `tui_click` to drive the UI
|
|
5. **Assert** — `tui_screenshot` for visual verification or check `tui_text` output
|
|
6. **Cleanup** — `tui_close` to terminate the session
|
|
|
|
## Key Concepts
|
|
|
|
- **Accessibility snapshots** — structured element tree with references, preferred over raw text matching
|
|
- **Multi-session** — can run multiple TUI apps simultaneously for integration tests
|
|
- **Asciicast recording** — can record sessions for replay/debugging
|
|
- **JS scripting** — `tui_run_code` for complex programmatic interactions
|
|
|
|
## File Location
|
|
|
|
`/mnt/NV2/Development/claude-home/development/tui-testing.md`
|