// Use when you need to verify tui-use end-to-end behavior — driving interactive CLI programs, Python REPL, --text pattern matching, custom timeout, special key handling, and highlights detection.
Operate interactive terminal programs (REPLs, debuggers, TUI apps) using PTY automation. Use when you need to interact with programs that require keyboard input.
Operate interactive terminal programs (REPLs, installers, TUI apps) using PTY automation. Use when you need to interact with programs that require keyboard input.
Use when you need to verify tui-use's ability to drive git workflows — interactive rebase, conflict resolution with vim, and verifying repository state.
Use when you need to verify tui-use's ability to drive vim — opening files, editing text, navigation, undo/redo, search & replace, and saving.
| name | tui-use-integration-test |
| description | Use when you need to verify tui-use end-to-end behavior — driving interactive CLI programs, Python REPL, --text pattern matching, custom timeout, special key handling, and highlights detection. |
Run integration tests to verify tui-use functionality.
/tui-use-integration-test # Run all test suites
/tui-use-integration-test <suite> # Run specific test suite
| Suite | Description |
|---|---|
session | Session lifecycle: start, use, info, rename, list, kill |
interaction | User interaction: wait, type, press, paste, REPL |
find | Text search functionality with regex |
scroll | Terminal buffer scrolling |
highlights | Inverse-video highlights detection |
Test specifications are in tests/ directory
After running tests, report results as:
<suite>:
<scenario 1> — PARTIAL
- Initial screen capture: PASS
- scroll command executes: PASS
- Less pager scrolling with 'space': FAIL
<scenario 2> — PASS
- Find A words: PASS
- Find B words: FAIL (<Fail reason or notes>)
If any test fails, include the actual screen and highlights values and what was expected.