testing-expected-results

What problem does it solve?

This Skill ensures that commands not only exit successfully (exit code 0) but also produce the intended real-world outcomes and side effects, preventing "it ran without error but is still broken" scenarios.

Core Features & Use Cases

• Comprehensive State Capture: Records filesystem, process, and network states before and after command execution.
• Intelligent Comparison: Compares actual outcomes against expected results using exact matches, patterns, ranges, and semantic analysis.
• Side Effect Verification: Validates changes in files, databases, processes, and network activity.
• Async/Delayed Effect Handling: Supports polling and waiting for eventual consistency.
• Use Case: Debugging why a deployment command reported success but the application is unresponsive by verifying that the correct processes are running and ports are listening.

Quick Start

Use the testing-expected-results skill to verify that running './deploy.sh --version=v2.0.0' results in the 'my-service' process running and listening on port 8080.