Add ty TUI QA harness (scripts/qa)#554
Merged
Merged
Conversation
A small harness to drive the actual TUI against a throwaway, isolated instance (separate DB + tmux sessions + projects_dir), so features can be QA'd via real keystrokes and asserted via --debug-state-file instead of manual one-offs. Loop: up -> key -> assert state -> down. ty-qa-up / -tui / -key / -state / -capture / -down, plus ty-qa-agent.sh which attaches a live agent window for pane/detail-view tests without a daemon (ty's daemon lock is global, so a second daemon can't run beside the live one). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A small harness to drive the real ty TUI against a throwaway, isolated instance — separate DB, tmux sessions, and
projects_dir— so we can QA features with real keystrokes and assert on real UI state instead of manual one-offs.Loop: up → key → assert state → down.
ty-qa-up.shty-qa-tui.shtask-ui-qawith--debug-state-filety-qa-key.shP Enter,n,!, …)ty-qa-state.shty-qa-capture.shty-qa-agent.shty-qa-down.shWhy now
Several recently-merged PRs (worktree auto-clean/restore, new-project creation, the pane-routing fix in #553) really needed real-TUI verification. This makes that repeatable.
ty-qa-agent.shexists because ty's daemon lock is global (~/.local/share/task/daemon.pid) — you can't run a second daemon beside the live one — so it stands up an agent window and points the task's DB row at it, letting the TUI exercise the realjoinTmuxPane/ nudge / shell-pane paths without a daemon. Seescripts/qa/README.mdfor the three test tiers.Test plan
Dogfooded end-to-end:
up→ create task →ty-qa-agent.sh 1→ty-qa-tui.sh→ty-qa-key.sh P Enter→ty-qa-state.shreportsdetail.has_panes: trueand the agent pane physically joins intotask-ui-qa. All scripts passbash -n.🤖 Generated with Claude Code