Accelerating development cycles with a lightweight CLI testing tool

During the development of a Python-based system (e.g., FastMCP 2.0), reliance on email services (e.g., AWS SES/SNS) for testing introduced unacceptable delays (10-30 seconds per test) and operational complexity. This solution replaced the email workflow with a lightweight CLI tool to accelerate iteration and streamline debugging.

Issue

The email-based testing workflow created critical bottlenecks:

• Slow feedback loops: Each test required an 8-step process (email → webhook → worker → database → AI inference → response → inbox), adding 10-30 seconds per iteration.
• Complex setup: Developers needed valid email service credentials and properly configured webhook endpoints.
• Fragmented logs: Debugging required checking multiple services (webhooks, workers, email inboxes).
• Manual verification: Responses were only visible in email inboxes, lacking direct terminal output.

This architecture, optimized for production reliability, hindered rapid development and debugging of core components.

Culprit

The root cause was the reuse of a production-grade email workflow for local testing:

• Over-engineered path: Email → Webhook → Database → Workers → AI Services → Email Response.
• External dependencies: Required valid AWS SES/SNS configurations for testing.
• Log sprawl: Debugging spanned webhooks, workers, and email services.
• No direct feedback: Responses were not visible in the terminal or IDE.

Solution

A CLI tool was developed to bypass email infrastructure while preserving core system functionality. The tool:

1. Directly invokes the system’s processing logic without email intermediaries.
2. Returns responses to the terminal for immediate feedback.
3. Maintains compatibility with existing orchestration and AI components.

Key Features

• Reduced test path: CLI → System Core → AI Services → Terminal (eliminating 6 intermediate steps).
• Performance: Reduced test time from 10-30 seconds to 2-5 seconds (80-90% improvement).
• Simplified debugging: Consolidated logs and terminal output for direct validation.
• Resource efficiency: No external API calls or additional services required.

Technical Implementation

The CLI tool integrates with the system’s internal APIs to:

• Process test inputs without email dependencies.
• Return structured responses directly to the terminal.
• Support interactive and scripted testing modes.

Example Workflow

1. Interactive Mode: Launch a REPL-like interface for exploratory testing.
2. One-Shot Testing: Execute tests via command-line arguments for automation.
3. Custom Inputs: Simulate user requests with specific email addresses or parameters.

Deployment

The tool was deployed as a lightweight Kubernetes pod with minimal resource requirements (e.g., 256-512Mi RAM), ensuring compatibility with existing development environments.

This solution maintains full compatibility with the system’s core logic while eliminating the email infrastructure overhead, enabling faster development cycles and easier debugging.