e2e-testing

Name: e2e-testing
Availability: InStock
Author: uniquk

Verify Claudex CLI behavior across headless, interactive, MCP, and API workflows.

Updated Apr 21, 2026

Search Tags:#debugging #cli #e2e-testing #headless #tool-integration #mcp-testing #claudex

Ready to run

npx skills add https://github.com/uniQuk/Claudex-cli --skill e2e-testing-uniquk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/uniQuk/Claudex-cli/tree/main/.qwen/skills/e2e-testing
Command: npx skills add https://github.com/uniQuk/Claudex-cli --skill e2e-testing-uniquk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

End-to-end testing for the Claudex CLI, enabling verification of full workflows from prompt to model responses and tool interactions.

Core Features & Use Cases

Headless mode testing to capture JSON outputs and tool calls.
Interactive tmux/terminal sessions to validate UX and permissions prompts.
MCP server integration testing and raw API traffic inspection for debugging.

Quick Start

Run a complete e2e test for a bug report by executing the CLI with a representative prompt and reviewing the structured JSON results.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema

How do I run end-to-end tests for a CLI tool to validate full workflows?▼

To run end-to-end tests for a CLI tool, execute the CLI with a representative prompt and review structured JSON results to verify full workflows from prompt to model responses and tool interactions.

Can I capture tool calls and JSON outputs during headless CLI runs?▼

Yes, headless mode testing captures JSON outputs and tool calls. This allows you to validate the CLI's programmatic behavior and verify tool integrations without interactive terminal overhead.

How do I test interactive terminal sessions and validate UX permissions prompts?▼

Interactive tmux and terminal sessions validate UX and permissions prompts during CLI testing. This simulates real-world user interactions to ensure the CLI correctly handles permission requests and terminal flows.

Does this approach support MCP server integration testing and raw API traffic inspection?▼

Yes, MCP server integration testing and raw API traffic inspection are fully supported for debugging. You inspect raw API traffic to identify pipeline issues and ensure accurate tool integrations in real-world scenarios.

What is the best way to ensure reproducible test setups for CLI debugging?▼

The best way to ensure reproducible CLI debugging setups is to enforce structured outputs and clear tool integrations. This provides quality guarantees and consistent results across test runs.

What are the limitations of headless mode testing compared to interactive sessions?▼

Headless mode testing captures JSON outputs but cannot validate interactive UX and permissions prompts. For full pipeline verification, you must also run interactive tmux sessions to test terminal-based user interactions.