Imported as a linear vendor commit so forge rebases do not replay the upstream root tree. git-subtree-dir: third_party/pi git-subtree-split: 71023aec1546d6d677a65669c5665c0927ce0dd0
20 lines
930 B
Markdown
20 lines
930 B
Markdown
---
|
|
name: interactive-testing
|
|
description: Test and debug pi's interactive mode in a controlled tmux terminal. Use for TUI behavior checks and interactive release smoke tests.
|
|
---
|
|
|
|
# Testing pi Interactive Mode with tmux
|
|
|
|
Run the TUI in a controlled terminal (from the repo root, two directories above this skill):
|
|
|
|
```bash
|
|
tmux new-session -d -s pi-test -x 80 -y 24
|
|
tmux send-keys -t pi-test "./pi-test.sh" Enter
|
|
sleep 3 && tmux capture-pane -t pi-test -p # capture after startup
|
|
tmux send-keys -t pi-test "your prompt here" Enter
|
|
tmux send-keys -t pi-test Escape # special keys (also C-o for ctrl+o, etc.)
|
|
tmux kill-session -t pi-test
|
|
```
|
|
|
|
For release smoke tests, start the tmux session with `-c /tmp` and replace `./pi-test.sh` with the absolute path to the release binary. Test both Node and Bun binaries separately, submit a prompt, and wait for the model reply; startup alone is not a passing smoke test.
|