Production validation specialist ensuring applications are fully implemented
Scanned 9/9/2026
Install to Claude Code
npx -y skills add vamseeachanta/workspace-hub --skill testing-production --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Testing Production?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-testing-production)More formats (shields.io, HTML) on the badges page.
---
name: testing-production
description: Production validation specialist ensuring applications are fully implemented
and deployment-ready. Use to verify no mock/stub/fake implementations remain, validate
against real databases and APIs, perform end-to-end testing with actual systems,
and confirm production readiness.
version: 1.0.0
category: development
type: hybrid
capabilities:
- production_validation
- implementation_verification
- end_to_end_testing
- deployment_readiness
- real_world_simulation
- security_validation
- performance_under_load
tools:
- Read
- Write
- Bash
- Grep
- Task
related_skills:
- testing-tdd-london
- webapp-testing
- planning-code-goal
hooks:
pre: 'echo "Production Validator starting..."
echo "Scanning for mock/fake implementations..."
grep -r "mock\|fake\|stub\|TODO\|FIXME" src/ || echo "No mock implementations
found"
'
post: "echo \"Production validation complete\"\nif [ -f \"package.json\" ]; then\n\
\ npm run test:production --if-present\n npm run test:e2e --if-present\nfi\n"
requires: []
tags: []
---
# Testing Production
## Quick Start
```bash
# 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
- [Continuous Delivery](https://continuousdelivery.com/)
- [Testing in Production](https://launchdarkly.com/blog/testing-in-production/)
- [OWASP Testing Guide](https://owasp.org/www-project-web-security-testing-guide/)
## Version History
- **1.0.0** (2026-01-02): Initial release - converted from production-validator agent
## Sub-Skills
- [Configuration](configuration/SKILL.md)
- [Example 1: Complete Validation Suite (+2)](example-1-complete-validation-suite/SKILL.md)
- [Example 4: Security Validation](example-4-security-validation/SKILL.md)
- [Real Data Usage (+3)](real-data-usage/SKILL.md)
## Sub-Skills
- [Execution Checklist](execution-checklist/SKILL.md)
- [Error Handling](error-handling/SKILL.md)
## Sub-Skills
- [Production Validation vs Unit Testing (+1)](production-validation-vs-unit-testing/SKILL.md)
- [1. Implementation Completeness Check (+2)](1-implementation-completeness-check/SKILL.md)
- [Metrics & Success Criteria](metrics-success-criteria/SKILL.md)
- [MCP Tools (+2)](mcp-tools/SKILL.md)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!