setup-comprehensive-testing — Claude Code command: test setup
This command builds a layered testing setup and connects it to CI. Use it when a project needs unit, integration, browser, visual, or performance checks.
npx claude-code-templates@latest --command testing/setup-comprehensive-testingWhat setup-comprehensive-testing does
setup-comprehensive-testing inspects the project before changing it: it checks the project type, test files, CI markers, and references to known frameworks. Its work is controlled by an argument such as --unit, --integration, --e2e, --visual, --performance, or --full-stack. The command can read and edit files and run shell checks through Read, Write, Edit, and Bash.
The setup covers unit runners such as Jest, Vitest, and pytest, plus integration tests with test databases and API checks. It can configure Cypress or Playwright for browser flows, visual regression, performance benchmarks, accessibility checks, and CI/CD execution with parallel tests and quality gates. Contract, chaos, load, security, cross-browser, and mobile testing are listed as advanced areas. The command needs Bash access to run its project checks and setup commands.
What it helps with
- design a testing pyramid for the project
- configure Jest, Vitest, or pytest
- add isolated integration and API checks
- prepare Cypress or Playwright browser flows
- connect test runs to CI/CD
Example prompts for the agent
- Set up layered testing for the whole project with
/testing:setup-comprehensive-testing --full-stack. - Configure unit testing with
/testing:setup-comprehensive-testing --unit. - Add browser checks for the
checkoutarea using/testing:setup-comprehensive-testing checkout --e2e.
How to install setup-comprehensive-testing
1claude-code-templates
npx claude-code-templates@latest --command testing/setup-comprehensive-testing2Manually: put the files in place
.claude/commands/setup-comprehensive-testing.mdCall it with /setup-comprehensive-testing. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/setup-comprehensive-testing.mdCall it with /prompts:setup-comprehensive-testing. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/setup-comprehensive-testing.prompt.mdManually: put the files in place
.gemini/commands/setup-comprehensive-testing.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about setup-comprehensive-testing
How do I install setup-comprehensive-testing in Claude Code?
Run npx claude-code-templates@latest --command testing/setup-comprehensive-testing, then use .claude/commands/setup-comprehensive-testing.md.
What does setup-comprehensive-testing do?
It inspects the current project and sets up selected testing layers: unit, integration, e2e, visual, performance, or full-stack. It also connects test execution to CI/CD and quality gates.
Which frameworks can setup-comprehensive-testing configure?
The command names Jest, Vitest, and pytest for unit testing, and Cypress or Playwright for browser testing.
Source text
setup-comprehensive-testing.md · MIT
--- allowed-tools: Read, Write, Edit, Bash argument-hint: "[scope] | --unit | --integration | --e2e | --visual | --performance | --full-stack" description: Setup complete testing infrastructure with framework configuration and CI integration --- # Setup Comprehensive Testing Setup complete testing infrastructure with multi-layer testing strategy: **$ARGUMENTS** ## Current Testing Infrastructure - Project type: !`[ -f package.json ] && echo "Node.js" || [ -f requirements.txt ] && echo "Python" || [ -f pom.xml ] && echo "Java" || echo "Multi-language"` - Existing tests: !`find . -name "*.test.*" -o -name "*.spec.*" | wc -l` test files - CI system: !`find . -name ".github" -o -name ".gitlab-ci.yml" -o -name "Jenkinsfile" | head -1 || echo "No CI detected"` - Framework: !`grep -l "jest\\|vitest\\|pytest\\|junit" package.json requirements.txt pom.xml 2>/dev/null | head -1 || echo "Detect framework"` ## Task Implement comprehensive testing infrastructure with multi-layer testing strategy: **Setup Scope**: Use $ARGUMENTS to focus on unit, integration, e2e, visual, performance testing, or full-stack implementation **Comprehensive Testing Framework**: 1. **Testing Strategy Design** - Analyze project requirements, define testing pyramid, plan coverage goals, optimize testing investment 2. **Unit Testing Setup** - Configure primary framework (Jest, Vitest, pytest), setup test runners, implement test utilities, optimize execution 3. **Integration Testing** - Setup integration test framework, configure test databases, implement API testing, optimize test isolation 4. **E2E Testing Configuration** - Setup browser testing (Cypress, Playwright), configure test environments, implement page objects 5. **Visual & Performance Testing** - Setup visual regression testing, configure performance benchmarks, implement accessibility testing 6. **CI/CD Integration** - Configure automated test execution, setup parallel testing, implement quality gates, optimize pipeline performance **Advanced Features**: Contract testing, chaos engineering, load testing, security testing, cross-browser testing, mobile testing. **Infrastructure Quality**: Test reliability, execution performance, maintainability, scalability, cost optimization. **Output**: Complete testing infrastructure with configured frameworks, CI integration, quality metrics, and maintenance workflows.
© davila7 · MIT · davila7/claude-code-templates