// Use when you need to verify tui-use's ability to drive vim — opening files, editing text, navigation, undo/redo, search & replace, and saving.
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.
| name | tui-use-vim-test |
| description | Use when you need to verify tui-use's ability to drive vim — opening files, editing text, navigation, undo/redo, search & replace, and saving. |
Run tests to verify tui-use can drive vim for real editing tasks.
/tui-use-vim-test # Run all test suites
/tui-use-vim-test <suite> # Run specific test suite
| Suite | Description |
|---|---|
edit | Create file, insert text, save, verify content |
navigate | Line jumping, undo, redo with ctrl+r |
substitute | Global search & replace with :%s |
Test specifications are in tests/ directory.
After running tests, report results as:
<suite>:
<scenario> — PASS / FAIL / PARTIAL
- <step description>: PASS / FAIL (<reason or actual output>)
If any test fails, include the actual screen content and what was expected.