菜单
Plan and design test environment strategies. Use when setting up testing infrastructure and environment requirements.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/sethdford/claude-skills --skill test-environment-plan命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Identify and avoid common architectural mistakes. Recognize patterns of failure. Use when reviewing designs or learning from mistakes.
Practice architectural design with structured problems. Time-limited design challenges. Use for skill development, interviews, team exercises.
Reference catalog of proven architecture patterns. Know when to apply each pattern, tradeoffs, and examples. Use as reference when designing systems.
基于 SOC 职业分类
正在显示 SKILL.md
| name | test-environment-plan |
| description | Plan and design test environment strategies. Use when setting up testing infrastructure and environment requirements. |
Design test environments that support quality assurance objectives while managing cost and complexity.
You are a senior QA engineer planning test environment strategy for $ARGUMENTS. Test environments must support various testing needs: functional, performance, security, compatibility.
Define Environment Requirements: Based on testing needs (functional, performance, security, compatibility), specify environment characteristics: hardware specs, OS/browser versions, database versions, third-party service versions. Identify critical production components that must be present in test environments.
Design Environment Strategy: Decide on environment count and purpose: dev environment for rapid iteration, test environment for comprehensive testing, staging for pre-production validation, production for live data. Define data requirements per environment: masked production data, synthetic data, or fresh data.
Plan Data Management: Establish data provisioning: production data snapshots (regularly refreshed), synthetic data generators for specific scenarios, data masking for sensitive information. Define data reset procedures between test cycles. Document data dependencies and refresh frequency.
Implement Environment Provisioning: Automate environment setup using infrastructure-as-code (Terraform, CloudFormation, Docker). Document environment setup steps, configuration management, and recovery procedures. Enable self-service environment provisioning to reduce setup time and human error.
Establish Environment Maintenance: Define SLAs for environment availability, monitoring, incident response. Schedule regular updates for patches, security fixes, and dependency updates. Monitor resource utilization and performance. Document known environment issues and workarounds.
Insufficient environment parity — Development-focused test environments that differ significantly from production miss environment-specific defects. Guard: Regularly compare test/production configurations; use production-equivalent docker containers or VMs; test key integrations in staging.
Shared environment conflicts — Shared test environments without proper isolation lead to test interference and flaky tests. Guard: Isolate tests by data, by runner (separate VMs), or by environment (parallel test environments). Use containerization for isolation.
Static environments — Manually-maintained environments become inconsistent and unreliable. Guard: Automate environment provisioning; version control all configurations; rebuild environments regularly to catch configuration drift.
