QA Environment Checker

QA Environment Checker

Purpose

Verify that the test environment is ready for test execution. Checks service health, database connectivity, required accounts, configuration files, dependencies, and tool availability. Produces an environment readiness report with pass/fail per check, setup instructions for failures, and automated fix suggestions.

Trigger Phrases

• "Check test environment" / "Environment readiness"
• "Verify environment before tests" / "Pre-test environment check"
• "Is my test env ready?" / "Environment validation"
• "Check services, DB, config before running tests"
• "Environment setup verification"
• "Dependency check for tests"
• "Health check for test environment"

Checks Performed

See references/health-checks.md for service health patterns and references/dependency-matrix.md for dependency requirements by test type.

Output Format

Environment Readiness Report Template

# Environment Readiness Report

**Generated:** [timestamp]
**Target:** [project/env name]

## Summary
| Status | Count |
|--------|-------|
| Pass   | X     |
| Fail   | Y     |
| Skip   | Z     |

**Overall:** Ready / Not ready

## Checks

### [Category]: [Check name]
- **Status:** Pass / Fail / Skip
- **Details:** [output or error message]
- **Fix (if failed):** [setup instructions or command]
- **Auto-fix available:** Yes / No

## Failed Checks Summary
1. [Check] — [Brief fix]
2. [Check] — [Brief fix]

## Setup Instructions
[Step-by-step for failed checks]

## References
- Health checks: references/health-checks.md
- Dependency matrix: references/dependency-matrix.md

Workflow

1. Identify scope — User specifies project, test type (E2E, API, unit), or config path
2. Load dependency matrix — Use references/dependency-matrix.md for required tools per test type
3. Run checks — Execute health checks, connectivity tests, config validation
4. Collect results — Pass/fail per check with details
5. Generate report — Structured output per template
6. Provide fix suggestions — Setup instructions, commands, or automated fix scripts for failures

Integration with Other Skills

Scope

Can do (autonomous):

• Check service health (HTTP requests to health endpoints)
• Validate config files (syntax, required keys)
• Verify tool availability (which, version commands)
• Check env vars from .env (without exposing secrets)
• Produce readiness report with fix suggestions
• Reference health-checks and dependency-matrix

Cannot do (requires confirmation):

• Install dependencies or modify system (suggest only)
• Create accounts or credentials
• Run migrations (suggest commands only)
• Modify production or shared environments

Will not do (out of scope):

• Execute actual tests (only verify environment)
• Deploy or provision infrastructure
• Access restricted systems without permission
• Expose secrets in reports

References

Quality Checklist

• All relevant checks run per test type (see dependency-matrix)
• Report includes pass/fail and fix suggestions for failures
• No secrets exposed in report output
• Setup instructions are actionable (commands, steps)
• Skip reason documented when check skipped
• References to health-checks and dependency-matrix correct

Troubleshooting