managing-test-environments

This skill enables Claude to manage isolated test environments using Docker Compose, Testcontainers, and environment variables. It is used to create consistent, reproducible testing environments for software projects. Claude should use this skill when the user needs to set up a test environment with specific configurations, manage Docker Compose files for test infrastructure, set up programmatic container management with Testcontainers, manage environment variables for tests, or ensure cleanup after tests. Trigger terms include "test environment", "docker compose", "testcontainers", "environment variables", "isolated environment", "env-setup", and "test setup".

1.27x

Quality

53%

Does it follow best practices?

Impact

94%

1.27x

Average score across 12 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/test-environment-manager/skills/test-environment-manager/SKILL.md

Evaluation results

95%

-5%

Integration Test Infrastructure for a Node.js API

Docker Compose test infrastructure

Criteria

Without context

With context

docker-compose.yml filename

100%

Multiple services defined

100%

Database service present

100%

Cache/queue service present

100%

Environment variables for DB

100%

Environment variables for cache

100%

Isolation mechanism

100%

75%

Cleanup routine

100%

Port conflict avoidance

100%

Reproducibility aid

100%

75%

Setup documentation

100%

47%

Integration Tests for a User Repository Layer

Testcontainers programmatic setup

Criteria

Without context

With context

Testcontainers import

100%

Container started in test setup

28%

100%

Dynamic port binding

83%

100%

Environment variables set from container

28%

100%

Container stopped in teardown

57%

100%

No external Docker Compose dependency

100%

At least one integration test

100%

Dependency declaration

58%

100%

91%

-2%

Automated Testing Pipeline for a Message-Driven Microservice

CI/CD pipeline test environment

Criteria

Without context

With context

CI config file present

100%

docker-compose.yml used in CI

100%

docker-compose.yml file created

100%

RabbitMQ service defined

100%

Environment variables configured

100%

Env vars passed to test runner

100%

Teardown/cleanup step

100%

Isolation from other environments

70%

50%

Service health check or wait

100%

No hardcoded credentials

50%

95%

Notification Service: RabbitMQ Integration Tests

Testcontainers message queue integration

Criteria

Without context

With context

Testcontainers library used

100%

RabbitMQ container started programmatically

100%

Dynamic port retrieval

100%

Env vars from container object

83%

100%

Container stopped in teardown

100%

No external Docker Compose dependency

100%

At least one integration test

100%

Testcontainers dependency declared

100%

Pinned image tag

50%

58%

87%

Search Service: Consistent Local Test Environment

Reproducible Docker Compose environment with non-standard service

Criteria

Without context

With context

docker-compose.yml present

100%

Elasticsearch service defined

100%

Pinned image version

100%

Env vars configured

100%

Environment isolation

41%

58%

Cleanup routine provided

100%

Port conflict avoidance

Health check or readiness mechanism

100%

Setup instructions provided

100%

No hardcoded credentials

100%

97%

51%

Session Analytics: Multi-Service Integration Tests

Testcontainers multi-container lifecycle management

Criteria

Without context

With context

Testcontainers used for both services

78%

Containers started in test setup

40%

100%

Dynamic ports retrieved for DB

50%

100%

Dynamic ports retrieved for cache

50%

100%

Env vars set from DB container

50%

100%

Env vars set from cache container

50%

100%

Both containers stopped in teardown

50%

100%

Integration test exercises both services

100%

Testcontainers dependency declared

100%

No Docker Compose reference

100%

98%

-2%

Test Environment Configuration for User Service

Environment variable isolation for test environments

Criteria

Without context

With context

docker-compose.yml filename

100%

Separate env config file

100%

DB env vars in config file

100%

Redis env vars in config file

100%

80%

No hardcoded credentials

100%

Isolation mechanism

100%

Cleanup routine

100%

Setup documentation

100%

Test-specific database name

100%

84%

Reliable Integration Test Environment for Order Processing Service

Docker Compose service health checks and startup ordering

Criteria

Without context

With context

docker-compose.yml present

100%

PostgreSQL healthcheck defined

100%

RabbitMQ healthcheck defined

100%

depends_on with service_healthy

Environment variables configured

100%

Isolation mechanism

100%

Cleanup routine with volume removal

100%

Pinned image versions

100%

Setup instructions provided

100%

85%

Integration Tests for Content Platform Document Storage Layer

Testcontainers document database integration tests

Criteria

Without context

With context

Testcontainers library used

100%

MongoDB container started programmatically

100%

Dynamic connection string from container

100%

Env vars or client configured from container

100%

Container stopped in teardown

100%

No Docker Compose dependency

100%

At least one integration test

50%

100%

Testcontainers dependency declared

100%

Pinned MongoDB image version

100%

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 13d35b8

Evaluated: about 2 months ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Integration Test Infrastructure for a Node.js API Integration Tests for a User Repository Layer Automated Testing Pipeline for a Message-Driven Microservice Notification Service: RabbitMQ Integration Tests Search Service: Consistent Local Test Environment Session Analytics: Multi-Service Integration Tests Test Environment Configuration for User Service Reliable Integration Test Environment for Order Processing Service Integration Tests for Content Platform Document Storage Layer

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.