Integration Test Command
Description
Execute comprehensive integration test suite with multi-component coordination and validation.
Installation
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open the source below and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
Repository README
This is the README for ruvnet/QuDAG, shared by 10 entries
in this directory. It describes the repository, not this entry specifically.
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:
**Load integration context and test history**:
- Read
.claude/contexts/integration_context.mdfor current integration state - Review
.claude/contexts/test_status.mdfor recent test results - Identify component dependencies and integration points
- Read
**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
**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 integrationStress 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 integrationAdversarial 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 resiliencePerformance 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**Aggregate results from all components**:
- Collect test results from each component
- Build component interaction matrix
- Analyze integration point failures
- Generate coverage metrics
**Analyze inter-component dependencies**:
- Map data flow between components
- Verify state consisten
Related Skills
Spec Kit
💫 Toolkit to help you get started with Spec-Driven Development
Testing Webapp Testing
Test local web applications using Playwright for UI verification and debugging
Testing #29
, [#52](https://github.com/affaan-m/everything-claude-code/issues/52), [#103](https://github.com/affaan-m/ever
Testing Fix Issue
by metabase - Addresses GitHub issues by taking issue number as parameter, analyzing context, implementing sol
Testing Pypict Test Design
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for optimized test sui
Testing gstack
| 15,000+ | Garry Tan's exact Claude Code setup: 6 opinionated tools that serve as CEO, Eng Manager, Release M
Testing