cli-e2e-testing

Automate Aspire CLI end-to-end tests using Hex1b terminal scripting.

6.2k|952|Updated Sep 25, 2023
One-click install
npx skills add https://github.com/dotnet/aspire --skill cli-e2e-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-e2e-testing
Source: https://github.com/dotnet/aspire/tree/main/.github/skills/cli-e2e-testing
Command: npx skills add https://github.com/dotnet/aspire --skill cli-e2e-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aspire CLI end-to-end tests require deterministic terminal automation to reliably validate command flows, prompt handling, and CI integration.

Core Features & Use Cases

Core components include Hex1bTerminal, Hex1bTerminalInputSequenceBuilder, CellPatternSearcher, SequenceCounter, CliE2ETestHelpers, and TemporaryWorkspace. The skill demonstrates building test architectures that run in headless Linux environments and capture asciinema recordings for debugging.

Quick Start

Create a minimal test skeleton that launches a headless Hex1b terminal, executes a simple command like aspire --version, and waits for a success prompt before exiting.

Frequently Asked Questions about cli-e2e-testing

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

FAQPage Schema
How do I automate CLI end-to-end testing for interactive prompts in CI pipelines?

CLI end-to-end testing for interactive prompts is automated using the Hex1b library to script terminal interactions and match deterministic outputs. This approach stabilizes command flows and long-running processes within Linux CI pipelines.

How does terminal automation handle interactive prompts in headless Linux environments?

Terminal automation in headless Linux environments uses a Hex1b terminal input sequence builder and cell pattern searcher to drive interactive prompts deterministically. It captures asciinema recordings to provide debugging context for the automated test runs.

Can I use asciinema recordings to debug failing CLI e2e tests?

Yes, asciinema recordings are integrated directly into the test architecture to debug failing CLI e2e tests. The structured workflow captures terminal sessions during execution, providing precise playback for analyzing command flows and prompt handling failures.

What is the best way to validate command flows and prompt handling in a CLI?

The best way to validate CLI command flows and prompt handling is by building a structured test architecture with Hex1b. It uses pattern matching and sequence counters to exercise commands across a temporary workspace, ensuring deterministic prompt validation.

Does this CLI testing approach work for local development or is it limited to CI?

This CLI testing approach works for both local development and CI pipelines. It launches a headless Hex1b terminal to execute commands and validate success prompts, applying the same deterministic automation workflow across Linux environments.