tui-test

Name: tui-test
Availability: InStock
Author: gtpgg1013

Automate end-to-end TUI testing workflows with ink-testing-library and vitest.

Updated Mar 21, 2026

Search Tags:#automation #vitest #testing #test-generation #tui #ink-testing-library

Ready to run

npx skills add https://github.com/gtpgg1013/claude-skills-collection --skill tui-test-gtpgg1013

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tui-test
Source: https://github.com/gtpgg1013/claude-skills-collection/tree/main/skills/claude-local/tui-test
Command: npx skills add https://github.com/gtpgg1013/claude-skills-collection --skill tui-test-gtpgg1013

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, multi-phase workflow to test ockemon-pso's TUI by performing gap analysis, generating ink-testing-library + vitest tests, and guiding iterative diagnosis and fixes to improve test coverage and reliability.

Core Features & Use Cases

Gap analysis and test design across 27 components, 16 hooks, and 4 animation modules.
Deterministic execution with mock patterns and phase-driven roles (test-engineer, executor, architect, qa-tester, verifier).
Targeted testing (app.tsx, use-menu, feed-panel, play-panel) and full-suite regression testing.

Quick Start

Run tui-test with a target (for example app or use-menu) to analyze TUI gaps, generate tests, and iterate through the architect-executor cycle until all tests pass.

Frequently Asked Questions about tui-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate TUI testing for ink-based apps using vitest?▼

You can automate TUI testing by applying a multi-phase workflow that uses ink-testing-library and vitest to perform gap analysis, generate targeted tests, and iterate through diagnosis cycles. This ensures deterministic execution with mock patterns and keyboard input simulations.

What is the process for generating tests for ink components and hooks?▼

Test generation for ink components involves a phase-driven orchestration workflow where an architect designs tests, an executor runs them, and a verifier checks results. This structured cycle targets specific components and hooks to iteratively improve test coverage and reliability.

Can I use ink-testing-library to simulate keyboard input in TUI tests?▼

Yes, ink-testing-library supports keyboard input simulations within deterministic test execution cycles. By integrating mock patterns, you can reliably simulate and validate user interactions across TUI components without flaky behavior.

Does this automated testing workflow support full-suite regression testing?▼

Yes, the workflow supports both targeted testing for specific modules and full-suite regression testing. It applies deterministic execution with mock patterns across all components, hooks, and animation modules to ensure comprehensive coverage and reliability.

What's the best way to perform gap analysis for TUI component test coverage?▼

The best way to perform gap analysis is using a structured workflow that evaluates existing test coverage across all components and hooks, identifies untested paths, and generates ink-testing-library and vitest tests to fill those gaps through iterative diagnosis and fixes.

Why do my ink-testing-library tests fail with non-deterministic results?▼

Non-deterministic tests often fail due to missing mock patterns or improper keyboard input simulations. Applying a phase-driven orchestration workflow with deterministic execution cycles and mock patterns ensures reliable test runs and iterative diagnosis of failures.