73 lines
2.5 KiB
Markdown
73 lines
2.5 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:40.739932+00:00"
|
|
relations:
|
|
- target: 62ee21e8-2b56-4d38-a73d-47e2724f08c6
|
|
type: RELATED_TO
|
|
direction: outgoing
|
|
strength: 0.71
|
|
edge_id: cc037348-44c5-467e-a9f1-8866bd4773c2
|
|
- target: 8e2d1904-24e0-41df-95f2-2edc4407b9f3
|
|
type: RELATED_TO
|
|
direction: outgoing
|
|
strength: 0.76
|
|
edge_id: e90568a0-c9d3-47a8-9a67-7c26fe7644fa
|
|
- target: a8f740ab-872b-4d2a-b652-c541a4519cb4
|
|
type: RELATED_TO
|
|
direction: outgoing
|
|
strength: 0.74
|
|
edge_id: 6a426497-2855-44a4-83c6-4e8c3e724fbb
|
|
- target: 967ad46d-ba89-4207-b870-db4b8558f2bb
|
|
type: CAUSES
|
|
direction: incoming
|
|
strength: 0.8
|
|
edge_id: a3078299-6baa-46a4-9d52-aa814b23dace
|
|
- target: 230a1d01-d47b-46ee-91f1-7388e3255b19
|
|
type: CAUSES
|
|
direction: incoming
|
|
strength: 0.7
|
|
edge_id: 16da3c73-9895-4147-943a-d41786178394
|
|
- target: 21be13ae-c01b-4bf1-917a-9e1ef18312a8
|
|
type: RELATED_TO
|
|
direction: outgoing
|
|
strength: 0.5
|
|
edge_id: 9af73e88-2f70-4109-99f9-bc2214d2a566
|
|
---
|
|
|
|
# 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`
|