CODITECT Testing Components
Version: 1.0.0 Last Updated: December 22, 2025
Overview
CODITECT provides specialized H.P.001-AGENTS, H.P.002-COMMANDS, H.P.003-SKILLS, and H.P.005-HOOKS for testing and quality assurance. This guide catalogs all testing-related components.
Testing Agents
codi-qa-specialist
Quality assurance specialist for comprehensive testing strategies.
Task(
subagent_type="codi-qa-specialist",
prompt="Create test plan for the new authentication module"
)
Capabilities:
- Test automation frameworks
- Performance testing
- Quality gate implementation
- Production validation
codi-test-engineer
Test engineering specialist for TDD and test infrastructure.
Task(
subagent_type="codi-test-engineer",
prompt="Implement unit tests for the API endpoints"
)
Capabilities:
- Test-driven development
- Continuous testing
- Quality engineering
- Test infrastructure
testing-specialist
Comprehensive test guardian and quality gate enforcer.
Task(
subagent_type="testing-specialist",
prompt="Validate 95% test coverage for the core module"
)
Capabilities:
- TDD compliance validation
- Quality gate enforcement
- Security, performance, accessibility validation
- Binary PASS/FAIL gate decisions
rust-qa-specialist
Rust-specific quality assurance.
Task(
subagent_type="rust-qa-specialist",
prompt="Review Rust code for safety and performance"
)
Capabilities:
- Memory safety validation
- Performance review
- Security analysis
- Production readiness
penetration-testing-agent
Security penetration testing specialist.
Task(
subagent_type="penetration-testing-agent",
prompt="Conduct authorized security assessment"
)
Capabilities:
- Vulnerability assessment
- Web application security
- API security validation
- Infrastructure analysis
Testing Skills
e2e-testing
End-to-end testing patterns with Playwright and Cypress.
skill: "e2e-testing"
Patterns:
- Page object model
- Test organization
- Flaky test handling
- CI integration
- Cross-browser testing
visual-regression
Visual regression testing with Percy and Chromatic.
skill: "visual-regression"
Patterns:
- Baseline management
- Threshold H.P.009-CONFIGuration
- CI integration
- Screenshot comparison
contract-testing
Consumer-driven contract testing with Pact.
skill: "contract-testing"
Patterns:
- API contracts
- Schema validation
- Provider verification
- CI integration
load-testing
Load testing with k6, Artillery, Locust.
skill: "load-testing"
Patterns:
- Performance validation
- Stress testing
- Capacity planning
- Threshold definitions
security-audit
OWASP Top 10 security auditing.
skill: "security-audit"
Patterns:
- SAST integration (Semgrep, Bandit)
- Vulnerability scanning
- Security assessments
Testing Commands
/security-scan
Execute comprehensive security scanning.
/security-scan
Executes:
- SAST analysis
- Dependency vulnerabilities
- Secrets detection
- Security misH.P.009-CONFIGuration analysis
/dependency-audit
Comprehensive dependency vulnerability auditing.
/dependency-audit
Executes:
- npm audit, pip-audit, cargo audit
- CVE reporting
- Upgrade recommendations
- License compliance
/perf-profile
Performance profiling for applications.
/perf-profile
Executes:
- CPU, memory, I/O analysis
- Flame graph generation
- Bottleneck identification
/lint-docs
Documentation quality checks.
/lint-docs
Executes:
- markdownlint
- YAML frontmatter validation
- Link checking
- Quality scoring
Testing Hooks
pre-commit-quality
Quality checks before commits.
Triggers: git commit
Actions:
- Run test suite (quick mode)
- Lint validation
- Security scan
pre-push-submodule-check
Submodule validation before push.
Triggers: git push
Actions:
- Submodule sync status
- Pointer validation
- Integration checks
Test Suite Script
H.P.004-SCRIPTS/test-suite.py
Main comprehensive test suite.
python3 H.P.004-SCRIPTS/test-suite.py # All tests
python3 H.P.004-SCRIPTS/test-suite.py -c H.P.001-AGENTS # Single category
python3 H.P.004-SCRIPTS/test-suite.py --verbose # Detailed output
Categories: 34
Tests: 4,714+
Output: test-results/
H.P.004-SCRIPTS/run-tests.sh
Shell wrapper for test execution.
./H.P.004-SCRIPTS/run-tests.sh
Quality Gate Integration
Recommended Quality Gates
| Gate | Threshold | Blocking |
|---|---|---|
| Pass Rate | 100% | Yes |
| Test Coverage | 80%+ | Yes |
| Security Issues | 0 Critical | Yes |
| Lint Errors | < 100 | No |
| Type Errors | < 50 | No |
CI/CD Integration
# Quality gate check
- name: Run test suite
run: python3 H.P.004-SCRIPTS/test-suite.py
- name: Check pass rate
run: |
PASS_RATE=$(jq '.summary.pass_rate' test-results/test-results.json)
if [ "$PASS_RATE" != "100.0" ]; then
echo "Pass rate below 100%"
exit 1
fi
Best Practices
For Test Development
- Use appropriate test status (FAIL for blockers, WARN for info)
- Provide clear error messages
- Include file paths in results
- Keep tests fast (< 30s each)
For Quality Assurance
- Run tests before every commit
- Review test results in CI
- Fix failures immediately
- Add tests for new features
For Security Testing
- Regular dependency audits
- SAST integration in CI
- Secrets detection in pre-commit
- Penetration testing quarterly
Related Documentation
- TEST-CATEGORIES.md - Category reference
- TEST-AUTOMATION.md - Automation guide
- COMPONENT-REFERENCE.md - All components
- USER-TROUBLESHOOTING.md - Troubleshooting