Integration Test Command — Testing skill for Claude Code

Integration Test Command

Execute comprehensive integration test suite with multi-component coordination and validation.

Usage

`/integration-test [scope] [components] [scenario]`

Parameters

• scope (optional): Test scope - full, quick, crypto-network, dag-protocol, network-protocol, end-to-end (default: full)
• components (optional): Specific components to test together - crypto, dag, network, protocol (comma-separated)
• scenario (optional): Integration test scenario - basic, stress, adversarial, performance (default: basic)

Instructions

When this command is invoked:

1. **Load integration context and test history**:

   • Read .claude/contexts/integration_context.md for current integration state
   • Review .claude/contexts/test_status.md for recent test results
   • Identify component dependencies and integration points

2. **Coordinate multi-agent test execution**:

   • Activate integration_agent as primary coordinator
   • Delegate component-specific tests to specialist agents:
     • crypto_agent: Cryptographic integration validation
     • network_agent: Network layer integration testing
     • consensus_agent: DAG consensus integration
     • security_agent: Security validation across components
     • performance_agent: Integration performance analysis

3. **Execute integration test scenarios**:

   Basic Scenario

   # Component initialization and setup
   cargo test --test integration_basic --features integration
   
   # Inter-component communication tests
   cargo test --test component_communication --features multi-component
   
   # State synchronization verification
   cargo test --test state_sync --features integration

   Stress Scenario

   # High-load multi-component stress testing
   cargo test --test integration_stress --features stress-test
   
   # Concurrent operation testing
   cargo test --test concurrent_ops --features multi-threaded
   
   # Resource exhaustion tests
   cargo test --test resource_limits --features integration

   Adversarial Scenario

   # Byzantine behavior simulation
   cargo test --test byzantine_tests --features adversarial
   
   # Attack scenario validation
   cargo test --test attack_scenarios --features security
   
   # Recovery mechanism testing
   cargo test --test failure_recovery --features resilience

   Performance Scenario

   # Integration performance benchmarks
   cargo bench --bench integration_bench
   
   # End-to-end latency measurement
   cargo bench --bench e2e_latency
   
   # Throughput under integration load
   cargo bench --bench integration_throughput

4. **Aggregate results from all components**:

   • Collect test results from each component
   • Build component interaction matrix
   • Analyze integration point failures
   • Generate coverage metrics

5. **Analyze inter-component dependencies**:

   • Map data flow between components
   • Verify state consisten