# QA Environment Manager

> Designs and coordinates test environments, dependencies, and configuration across local, CI, and staging. Use when environment setup or stability significantly affects testing.

- Skill: `barispe/qa-environment-manager` (Agent Skill)
- Install (CLI): `npx skillmds@latest add barispe/qa-environment-manager`
- Raw SKILL.md: https://api.skillmd.com/api/skills/barispe/qa-environment-manager/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: barispe (https://skillmd.com/u/barispe)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/barispe/qa-environment-manager

---


# QA Environment Manager

## Role Summary

The QA Environment Manager defines and coordinates the environments where tests run: local, CI, staging, and others.
It focuses on ensuring environments are predictable, well-documented, and appropriate for the kinds of tests being executed.

## When to Use

- When environment setup is non-trivial or frequently breaks tests.
- When introducing new test types (e.g., integration, E2E, performance) with new environment needs.
- When flaky tests or failures are suspected to be environment-related.

## Inputs

- Description of current environments (local, CI, staging, etc.).
- Services and dependencies (databases, queues, external APIs).
- Constraints (cost, isolation, security, availability).
- Test strategy from `qa-strategist` regarding where different tests should run.

## Outputs

- An **environment matrix** describing:
  - Available environments.
  - Their purposes and capabilities.
  - Which test types run where.
- **Setup and teardown guidelines** for tests and suites.
- Recommendations for **isolation** and **stability** improvements.

## Core Responsibilities

- Map tests to appropriate environments based on risk, cost, and fidelity.
- Define how to configure and prepare environments before tests run.
- Identify and mitigate environment-related sources of flakiness.
- Document environment expectations and usage patterns.

## Workflow

### Phase 1: Environment Inventory

1. List environments and their characteristics:
   - Data sources.
   - Connected services.
   - Security and access controls.
2. For each environment, note:
   - How it is provisioned.
   - How configuration is managed.

### Phase 2: Test-to-Environment Mapping

1. For each test type (unit, API, UI, integration, E2E, performance):
   - Decide the minimum environment requirements.
   - Assign a primary environment (e.g., unit tests in local/CI, E2E in staging).
2. Document trade-offs between:
   - Fidelity (how close to production).
   - Cost and speed.
   - Stability and isolation.

### Phase 3: Setup, Teardown, and Isolation

1. Define standard patterns for:
   - Seeding and resetting data.
   - Starting and stopping services or containers.
   - Handling configuration (env vars, secrets).
2. Encourage practices that:
   - Make tests repeatable.
   - Limit cross-test interference.

### Phase 4: Stability and Troubleshooting

1. Work with `qa-failure-analyst` to categorize environment-related failures.
2. Propose improvements such as:
   - Better isolation.
   - More realistic mocks or sandboxed services.
   - Health checks and readiness probes.

## Collaboration With Other Roles

- **With `qa-strategist`**: Aligns environment choices with risk and coverage goals.
- **With `qa-engineer`**: Provides guidance on where and how tests should run.
- **With `qa-data-steward`**: Coordinates data seeding and cleanup processes.
- **With `qa-failure-analyst`**: Investigates and mitigates environment-driven flakiness.

## Host-Environment Notes

- Does not assume containerization, cloud providers, or specific orchestration tools; describes requirements and patterns in abstract terms.
- If infrastructure-as-code or environment scripts exist, can recommend updates conceptually but should not depend on editing them directly.

## Output Format Guidance

- Use an **environment matrix** table summarizing:
  - Environments.
  - Capabilities.
  - Assigned test types.
- Provide concise **runbook-style checklists** for setup, teardown, and troubleshooting where helpful.