testing_plan_integration — Claude Code command: what it does
Generates integration testing plans, assesses code testability, and suggests refactoring steps like dependency injection.
npx claude-code-templates@latest --command testing/testing_plan_integrationWhat testing_plan_integration does
The command inspects project files through Bash. It checks for Cargo.toml or package.json to detect Rust or Node.js environments. Then it finds existing test files matching *.test.* or *.spec.*. This sets the baseline.
The generated plan maps component boundaries, external mock strategies, and critical data flows. It handles contract testing, service virtualization, and Rust-style inline tests. The output also highlights opportunities for dependency injection.
The prompt declares tool permissions for Read, Write, Edit, and Bash. Without Bash access, Claude Code cannot inspect your repository structure.
What it helps with
- design integration test scenarios and critical path data flows
- identify tight component coupling before writing test suites
- plan mocking strategies and test doubles for third-party dependencies
- outline Rust-style inline tests for modular code verification
Example prompts for the agent
- /testing_plan_integration src/services/auth.ts --refactoring-suggestions
- /testing_plan_integration crates/parser --rust --inline
- /testing_plan_integration src/controllers/order.py integration
How to install testing_plan_integration
1claude-code-templates
npx claude-code-templates@latest --command testing/testing_plan_integration2Manually: put the files in place
.claude/commands/testing_plan_integration.mdCall it with /testing_plan_integration. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/testing_plan_integration.mdCall it with /prompts:testing_plan_integration. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/testing_plan_integration.prompt.mdManually: put the files in place
.gemini/commands/testing_plan_integration.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about testing_plan_integration
How to install testing_plan_integration in Claude Code?
Run npx claude-code-templates@latest --command testing/testing_plan_integration in your terminal.
What does testing_plan_integration do?
It analyzes target code testability, evaluates coupling, and generates an integration test plan with mock strategies and refactoring advice.
Which arguments does testing_plan_integration support?
You can supply target code paths alongside flags such as --rust, --inline, and --refactoring-suggestions.
Source text
testing_plan_integration.md · MIT
--- allowed-tools: Read, Write, Edit, Bash argument-hint: "[target-code] | [test-type] | --rust | --inline | --refactoring-suggestions" description: Create comprehensive integration testing plan with inline tests and refactoring recommendations --- # Testing Plan Integration Create integration testing plan with inline test strategy and refactoring suggestions: **$ARGUMENTS** ## Current Testing Context - Project type: !`[ -f Cargo.toml ] && echo "Rust project" || [ -f package.json ] && echo "Node.js project" || echo "Multi-language project"` - Test framework: !`find . -name "*.test.*" -o -name "*.spec.*" | head -3` existing tests - Target code: Analysis of $ARGUMENTS for testability assessment - Integration complexity: Assessment of component interactions and dependencies ## Task Execute comprehensive integration testing plan with testability analysis: **Planning Focus**: Use $ARGUMENTS to specify target code, test type requirements, Rust inline testing, or refactoring suggestions **Integration Testing Framework**: 1. **Code Testability Analysis** - Analyze target code structure, identify testing challenges, assess coupling levels, evaluate dependency injection 2. **Test Strategy Design** - Design integration test approach, plan inline vs separate test files, identify test boundaries, optimize test isolation 3. **Refactoring Assessment** - Identify testability improvements, suggest dependency injection, recommend interface abstractions, optimize component boundaries 4. **Test Case Planning** - Design integration scenarios, identify critical paths, plan data flow testing, assess error handling coverage 5. **Mock Strategy** - Plan external dependency mocking, design test doubles, identify integration boundaries, optimize test performance 6. **Execution Planning** - Design test execution order, plan test data management, optimize test environment setup, ensure test isolation **Advanced Features**: Rust-style inline testing, property-based integration tests, contract testing, service virtualization, chaos engineering integration. **Quality Assurance**: Test maintainability, execution performance, coverage optimization, feedback loop efficiency. **Output**: Comprehensive integration test plan with test case specifications, refactoring recommendations, implementation strategy, and quality metrics.
© davila7 · MIT · davila7/claude-code-templates
