test-environment-management

The test-environment-management skill provides a comprehensive framework for orchestrating test infrastructure in modern development lifecycles. It is designed for Quality Engineers, DevOps practitioners, and developers who need to bridge the gap between local development, CI pipelines, and staging environments. By leveraging Infrastructure as Code (IaC) and containerization, this skill eliminates the 'works on my machine' syndrome by enforcing strict parity between production and test environments, including operating system versions, database configurations, and service topologies.

• Containerization of test environments using Docker and Docker Compose to ensure reproducibility and consistency across team members and CI runners.

• Service virtualization using tools like WireMock to decouple tests from volatile external dependencies, ensuring stable and reliable test execution.

• Cost optimization strategies, including automated shutdown scripts for idle cloud instances, implementation of spot instances via Terraform/HCL, and resource usage monitoring.

• Infrastructure as Code integration for provisioning reproducible environments, supporting diverse types such as local, CI, staging, and ephemeral integration environments.

• Agent-driven orchestration that allows automated agents like qe-test-executor and qe-chaos-engineer to spawn, isolate, and tear down environments programmatically.

• To use this skill, ensure your repository contains Docker Compose definitions for test services and clear mapping for external service mocks.

• Use the provided fleet coordination patterns if you are managing complex environments requiring cross-agent communication (e.g., performance testers coordinating with chaos engineers).

• Inputs for this skill typically involve environment specifications, desired parity levels, and lifetime requirements; outputs include provisioned infrastructure, environment health status, and cost impact reports.

• Always define clear lifecycle boundaries for environments to prevent resource leakage; utilize the provided cron-based auto-shutdown templates for cloud providers like AWS.

• Regularly validate dev/prod parity by comparing container versions and environment variables to prevent drift that leads to false-negative test results.