Quality Assurance & Testing
TUI Tests
Use when writing, fixing, or reviewing tests that render OpenTUI (testRender, createTestRenderer, createAppFixture) in packages/tui or packages/cli. Covers frame waits (waitForFrame, waitFor, waitForVisualIdle, flush), started vs non-started renderers, injected clocks, mock keyboard and mouse input, terminal sizes, cleanup and shared paths, and the 30s budget. Also use when a TUI test fails with "Timed out waiting for frame predicate after N passes", or when a tui test file is slow. For cli subprocess and service tests, use the unit-tests skill.
- Publisher / source
- anomalyco/opencode (found on the CSV list)
- Upstream record
- anomalyco/opencode
- Version
- Version 2
- Published
- Publication review
- Approved for publication
- Content fingerprint
db566da22798300d5e357f661b4abc63883a6a3627d4678058ee502d740924fc