Test Environments
Design environment strategy for testing across dev.
Use Edge to load the skill test-environments from petrkindlmann/qa-skills for my task. If Edge is not set up, read getedge.cc/SKILL.md and ask me first.
2 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
What it does
- Design environment strategy for testing across dev, CI, preview, staging, and production : Docker Compose test infrastructure, multi-stage Dockerfiles, seed-data lifecycle, per-PR preview environments, production parity, and external-dependency stubbing at the HTTP boundary.
- Use when: "set up test environment," "docker-compose for tests," "per-PR preview environment," "staging parity," "spin up test infra," "environment tiers." Not for: choosing mock-vs-stub-vs-fake per dependency : use service-virtualization; factory and fixture data patterns : use test-data-management; pipeline/Actions config : use ci-cd-integration.
- Related: test-data-management, ci-cd-integration, contract-testing, service-virtualization.
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads Test Environments.
Related skills
Test REST and GraphQL APIs with Playwright APIRequestContext, Supertest, or standalone HTTP clients. Covers schema validation with Zod 4/AJV, auth flow testing, CRUD lifecycle tests, error and header validation, paginati
OpenAI Codex CLI code review with GPT-5.2-Codex, CI/CD integration
Dockerize an application with a production-ready Dockerfile, docker-compose setup, and .dockerignore.
Use this skill when creating, modifying, or debugging Docker Compose configurations, even if the user just says they need to wire services together, add a database to their stack, or set up a local development environmen
Create optimized multi-stage Dockerfiles for any language or framework
Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose
No evidence record yet
No measured run with and without this skill yet, so this page makes no performance claim. 2 static scans, 0 counted findings. Security state at 2026-11-19: reviewed. Static scans check the code, not how well the skill works.
State definitionsSelect the Files tab to load SKILL.md.
Skill details
Security scansReviewed
2 static scans, 0 counted findings. Security state at 2026-11-19: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.2. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: not supplied.
Edge committed-secret checks (Edge-run): edge-secrets/1.0.0. Scope: Credentials committed in the skill's files (values never shown). Raw findings: not supplied.
Socket (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
Snyk (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
- Edge static checks
- Pass · 0 counted findings · 2026-11-19
- Edge committed-secret checks
- Pass · 0 counted findings · 2026-11-19
Creator, source & licencepetrkindlmann
From the petrkindlmann public repository. Edge did not write or edit this skill.
- Repository
- petrkindlmann/qa-skills
- Skill file
- View source at revision
- Revision
- b3bb61bd268b147476252c6ed5a0440c87b97441
- Package hash
- sha256:fa03d0083f1bd1bd30d6d3fb3628356883cf5d8336346ed19a4e52ed1edec730
- Licence
- MIT
- Description
- Design environment strategy for testing across dev, CI, preview, staging, and production : Docker Compose test infrastructure, multi-stage Dockerfiles, seed-data lifecycle, per-PR preview environments, production parity, and external-dependency stubbing at the HTTP boundary. Use when: "set up test environment," "docker-compose for tests," "per-PR preview environment," "staging parity," "spin up test infra," "environment tiers." Not for: choosing mock-vs-stub-vs-fake per dependency : use service-virtualization; factory and fixture data patterns : use test-data-management; pipeline/Actions config : use ci-cd-integration. Related: test-data-management, ci-cd-integration, contract-testing, service-virtualization.
Quoted from the skill’s own description
Read skill files3 files
3 files, 25.4 KB at revision b3bb61bd268b.
Questions about Test Environments
What does Test Environments do?
Design environment strategy for testing across dev. Published by petrkindlmann (petrkindlmann/qa-skills).
Is Test Environments safe to use?
Edge security state: Reviewed (2 Edge-run static scans, scanned Nov 19, 2026). The Evidence tab shows the scan.
How do I use Test Environments in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.