/smoke-test - Post-Deploy Smoke Test Execution
Executes post-deployment smoke tests to verify critical paths, health endpoints, and essential functionality. Provides fast feedback on deployment success and can trigger automatic rollback on failure.
System Prompt
EXECUTION DIRECTIVE: When the user invokes this command, you MUST:
- IMMEDIATELY execute - no questions first
- Load the skill at
skills/smoke-testing-patterns/SKILL.md - Identify the target environment (staging/production)
- Load critical path definitions from smoke-test manifests
- Execute health endpoint checks first (fail-fast)
- Run critical user journey tests in parallel
- Verify essential integrations (database, external APIs)
- Report results with pass/fail summary
- Trigger rollback if --rollback-on-failure and tests fail
- Output results in requested format
Usage
/smoke-test
/smoke-test --environment production
/smoke-test --critical-only --timeout 60
/smoke-test --rollback-on-failure --json
Options
| Option | Description |
|---|---|
--environment <env> | Target environment: staging, production (default: staging) |
--critical-only | Run only critical path tests (skip nice-to-have checks) |
--timeout <seconds> | Maximum duration for smoke test suite (default: 300) |
--rollback-on-failure | Automatically trigger rollback if smoke tests fail |
--json | Output results in JSON format for CI/CD integration |
--parallel <num> | Parallelization factor (default: 4) |
--include <pattern> | Include only tests matching pattern |
Related Commands
| Command | Relationship |
|---|---|
/release-gate | Smoke tests are post-deploy validation in release process |
/canary-check | Progressive rollout validation (complements smoke tests) |
/breaking-impact | Pre-deploy breaking change analysis |
/regression-check | Pre-deploy regression test selection |
Success Output
Smoke Test Suite - Production
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Health Endpoints:
✓ API Gateway /health (142ms)
✓ Database connectivity (89ms)
✓ Redis cache (34ms)
✓ External API reachability (256ms)
Critical Paths:
✓ User login flow (1.2s)
✓ Create document (0.8s)
✓ Search functionality (0.6s)
✓ Payment processing (2.1s)
Essential Integrations:
✓ S3 file storage (178ms)
✓ Email service (SendGrid) (423ms)
✓ Analytics (Segment) (91ms)
Results: 11/11 passed (0 failed, 0 skipped)
Duration: 5.4s
Status: DEPLOYMENT VERIFIED ✓
Deployment v1.23.4 is healthy and serving traffic.
Completion Checklist
- Environment identified and endpoints configured
- Health checks executed (fail-fast on unhealthy)
- Critical user journeys tested end-to-end
- Essential integrations verified
- Results reported with timing data
- Rollback triggered if tests failed and flag set
- Results exported in requested format
Failure Indicators
- "Health endpoint unreachable" → Deployment failed or networking issue
- "Critical path timeout" → Performance regression or infrastructure problem
- "Integration unavailable" → External dependency down
- "Rollback triggered" → Smoke tests failed with --rollback-on-failure
When NOT to Use
- Comprehensive testing - Use full regression suite instead
- Pre-deployment validation - Use /regression-check or /release-gate
- Load testing - Use dedicated performance testing tools
- Security testing - Use security scanning tools
Anti-Patterns
- Running comprehensive test suite as "smoke test" (defeats purpose of fast feedback)
- Skipping smoke tests because "CI passed" (different environments, different risks)
- Not defining critical paths (running arbitrary subset of tests)
- Ignoring smoke test failures ("probably a flaky test")
- Testing only happy paths (critical paths include error handling)
Principles
- #3 Complete Execution - Runs all smoke tests and reports results automatically
- #9 Based on Facts - Verifies actual endpoint health and user journey execution
Full Standard: CODITECT-STANDARD-AUTOMATION.md