sdlc-tui-test

Control terminal applications and evaluate CLI or TUI behavior against acceptance criteria.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-tui-test-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc-tui-test
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/sdlc-tui-test
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-tui-test-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying interactive terminal applications, CLI wizards, and TUI flows is hard to automate because prompts, inputs, outputs, and exit codes must be captured and judged against acceptance criteria. This Skill drives terminal applications like a user and produces transcripts, exit-code evidence, and pass/fail evaluations inside the Agentic SDLC workflow. ## Core Features & Use Cases - Pexpect-Style Interaction: Launch a CLI or TUI, wait for expected prompts, send inputs, and capture output and exit codes. - Evidence Capture: Record terminal transcripts, exit-code summaries, output assertions, and side-effect validation as run evidence. - Failure Classification: Map prompt mismatches, harness timeouts, and incorrect expected transcripts to evaluation, environment, or test defect categories. - Use Case: During a UAT evaluation of a CLI installer wizard, the coordinator routes to this Skill to drive the wizard, capture the full transcript, verify generated files, and return a pass/fail result against the acceptance criteria. ## Quick Start Ask the Agentic SDLC coordinator to evaluate the CLI wizard against its acceptance criteria using sdlc-tui-test and record the transcript and exit code as evidence.

Frequently Asked Questions about sdlc-tui-test

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

FAQPage Schema
How do I test a CLI wizard or TUI application automatically?

Use Pexpect-style interaction to launch the application, wait for expected prompts, send inputs, and capture output and exit codes. This Skill records the full transcript and evaluates it against acceptance criteria to produce a pass/fail result.

What evidence does terminal application testing produce?

Terminal testing produces a full interaction transcript, an exit-code summary, output assertions, and validation of generated files or side effects. These artifacts are stored as run evidence and compared against the acceptance criteria.

Can I use this Skill for browser GUI testing?

No, browser GUI flows are out of scope and should use the sdlc-gui-test skill instead. This Skill only covers terminal, CLI wizard, and TUI interaction.

Why is a zero exit code not enough to pass a TUI test?

A zero exit code only means the process exited normally, not that the required behavior occurred. When acceptance criteria require specific prompts, outputs, or side effects, the transcript and generated files must also be evaluated.

How are TUI test failures classified?

Prompt mismatches map to evaluation or implementation defects, harness timeouts map to environment defects unless output proves an application fault, and incorrect expected transcripts map to test defects. Every failure is classified before retrying or routing backward.