Testing Production
Quick Start
# Scan for incomplete implementations
grep -r "mock\|fake\|stub\|TODO\|FIXME" src/ --exclude-dir=__tests__
# Run production validation tests
npm run test:production
npm run test:e2e
# Validate against real services
npm run test:integration -- --env=staging
When to Use
- Before deploying to production
- After completing TDD implementation phase
- To verify no mock implementations remain in production code
- To test against real databases, APIs, and infrastructure
- To validate performance under realistic load
- To confirm security measures are properly implemented
Prerequisites
- Completed unit/integration test suite
- Access to staging environment with real services
- Environment variables for real service connections
- Load testing tools (if validating performance)
References
Version History
- 1.0.0 (2026-01-02): Initial release - converted from production-validator agent
Sub-Skills
- Configuration
- Example 1: Complete Validation Suite (+2)
- Example 4: Security Validation
- Real Data Usage (+3)
Sub-Skills
- Execution Checklist
- Error Handling
Sub-Skills
- Production Validation vs Unit Testing (+1)
- 1. Implementation Completeness Check (+2)
- Metrics & Success Criteria
- MCP Tools (+2)