agentsclimarketplace

Managing test environments

Skill jeremylongshore/claude-code-plugins-plus-skills/skills/.curated/managing-test-environments

425 plugins, 2,810 skills, 200 agents for Claude Code. Open-source marketplace at tonsofskills.com with the ccpi CLI package manager.

Install
npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill managing-test-environments

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

'Test provision and manage isolated test environments with configuration and data.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.9 KB, as published. Nobody here has run it

Test Environment Manager

Overview

Provision, configure, and manage isolated test environments for reliable test execution. Supports Docker Compose environments, Testcontainers, local service stacks, and ephemeral CI environments.

Prerequisites

  • Docker and Docker Compose installed (for containerized environments)
  • Testcontainers library installed if using programmatic container management
  • Database client tools (psql, mysql, mongosh) for seed data operations
  • Environment variable management via .env files or secrets manager
  • Sufficient disk space and memory for running service containers

Instructions

  1. Read the project's existing configuration files (docker-compose.yml, .env.test, jest.config.*, pytest.ini) to understand current environment setup.
  2. Inventory all external dependencies the test suite requires (databases, message queues, cache servers, third-party API stubs).
  3. Create or update a docker-compose.test.yml defining isolated service containers:
    • Assign non-conflicting ports to avoid collisions with development services.
    • Configure health checks for each service to prevent tests from starting before services are ready.
    • Set resource limits (memory, CPU) to match CI runner constraints.
  4. Write seed data scripts that populate databases with baseline test data:
    • Use idempotent migrations that can run repeatedly without error.
    • Create separate seed datasets for unit, integration, and E2E test tiers.
    • Include cleanup scripts that truncate tables without dropping schemas.
  5. Generate environment configuration files (.env.test) with connection strings, API keys, and feature flags appropriate for testing.
  6. Create a startup script that orchestrates the full environment lifecycle:
    • Start containers and wait for health checks to pass.
    • Run database migrations and seed data.
    • Export environment variables for the test runner.
    • Execute the test suite.
    • Tear down containers and clean up volumes.
  7. Validate the environment by running a small smoke test suite against the provisioned services.

Output

  • docker-compose.test.yml with all required service definitions
  • .env.test with test-specific configuration values
  • Database seed scripts (seeds/test-data.sql or equivalent)
  • Environment startup/teardown shell script (scripts/test-env.sh)
  • Health check verification report confirming all services are operational

Error Handling

ErrorCauseSolution
Port already in useAnother process or dev environment occupies the portUse dynamic port allocation or specify alternate ports in docker-compose.test.yml
Container health check timeoutService takes too long to initializeIncrease health check interval and retries; ensure sufficient memory allocation
Database seed failureMigration conflicts or missing schemaRun migrations before seeds; verify migration order; check for schema drift
Environment variable not found.env.test not loaded or variable misspelledVerify dotenv loading order; use env-cmd or dotenv-cli to inject variables
Stale Docker volumesPrevious test data persists across runsAdd --volumes flag to docker-compose down in teardown; use tmpfs mounts

Examples

Docker Compose test environment with PostgreSQL and Redis:

# docker-compose.test.yml
services:
  postgres-test:
    image: postgres:16-alpine
    environment:
      POSTGRES_DB: testdb
      POSTGRES_PASSWORD: testpass
    ports: ["5433:5432"]  # 5432: 5433: PostgreSQL port
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 2s
      retries: 10
  redis-test:
    image: redis:7-alpine
    ports: ["6380:6379"]  # 6379: 6380: Redis TLS port
    healthcheck:
      test: ["CMD", "redis-cli", "ping"]

Testcontainers setup in Jest:

import { PostgreSqlContainer } from '@testcontainers/postgresql';

let container;
beforeAll(async () => {
  container = await new PostgreSqlContainer().start();
  process.env.DATABASE_URL = container.getConnectionUri();
}, 30000);  # 30000: 30 seconds in ms
afterAll(async () => { await container.stop(); });

Resources

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.