cli-testing

Run automated Navigator CLI tests with bun and navigator-server.

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/outfitter-dev/navigator --skill cli-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-testing
Source: https://github.com/outfitter-dev/navigator/tree/main/.claude/skills/cli-testing
Command: npx skills add https://github.com/outfitter-dev/navigator --skill cli-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured framework for automated, repeatable Navigator CLI tests to catch regressions and ensure reliable command behavior across environments.

Core Features & Use Cases

  • Automated stress tests for Navigator CLI ensure robustness under complex command sequences.
  • Category-based test suites cover edge-cases, error handling, and real-world usage scenarios.
  • Reusable test templates and runner scripts enable fast QA feedback and regression checks.

Quick Start

Start the server with bun run dev and run the test suite using the provided CLAUDE testing scripts to exercise the Navigator CLI.

Frequently Asked Questions about cli-testing

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

FAQPage Schema
How do I automate CLI tests for Navigator command-line interactions?

Automating Navigator CLI tests involves running category-based test suites that validate command-line interactions and automation workflows. The framework applies marker-based scenarios and error-taxonomy checks to detect regressions across diverse environments.

What are stress tests for CLI automation and when do I need them?

Stress tests for CLI automation validate robustness under complex command sequences. They are needed when verifying that command-line interactions and automation workflows remain reliable across diverse environments and edge cases.

How do I run repeatable CLI regression tests using bun?

Repeatable CLI regression tests are run by starting the server with bun run dev and executing the provided CLIADE testing scripts. This setup leverages bun and navigator-server to exercise the Navigator CLI consistently.

Does Navigator CLI testing support edge-case and error-taxonomy checks?

Navigator CLI testing supports edge-case and error-taxonomy checks through category-based test suites. These suites cover real-world usage scenarios and error handling to detect regressions in command behavior.

What's the best way to validate command-line automation workflows without manual QA?

The best way to validate automation workflows without manual QA is using reusable test templates and runner scripts. These provide fast feedback by executing repeatable tests across edge-case and stress-test scenarios.