Integration testing with real dependencies in throwaway Docker containers using the Testcontainers Node.js API - GenericContainer, exposed ports, wait strategies, module containers, Docker Compose environments, and reliable cleanup.
npx skills add https://github.com/PramodDutta/qaskills --skill Docker Testcontainers
This skill makes an AI agent write integration tests that spin up real databases, caches, and message brokers in disposable Docker containers via the testcontainers Node.js library - instead of mocking them or depending on a shared dev server. Trigger it when tests need a real Postgres, Redis, Kafka, or any service with Docker image, when a repo already imports testcontainers, or when the user complains that mocked repositories keep hiding SQL and serialization bugs.
postgres:16-alpine, not latest).container.getMappedPort(5432) and container.getHost(); hardcoding localhost:5432 collides with local services and parallel CI jobs.Wait.forLogMessage, Wait.forListeningPorts, Wait.forHttp, or Wait.forHealthCheck so tests begin exactly when the dependency is usable.beforeAll, then reset state between tests with TRUNCATE, FLUSHALL, or transaction rollbacks - not by restarting the container.afterAll; Testcontainers' Ryuk sidecar reaps anything left behind if the process dies, so never disable it in CI.redis:latest changing under you turns a green suite red with zero code changes. Pin to a major-minor tag and upgrade deliberately.npm install --save-dev testcontainers @testcontainers/postgresql
# Requires a running Docker daemon (Docker Desktop, Colima, or CI's dockerd)
docker info
// tests/cache.integration.test.ts
import { GenericContainer, StartedTestContainer, Wait } from 'testcontainers';
import { createClient, RedisClientType } from 'redis';
describe('rate limiter backed by Redis', () => {
let container: StartedTestContainer;
let client: RedisClientType;
beforeAll(async () => {
container = await new GenericContainer('redis:7.4-alpine')
.withExposedPorts(6379)
.withWaitStrategy(Wait.forLogMessage('Ready to accept connections'))
.withStartupTimeout(30_000)
.start();
client = createClient({
url: `redis://${container.getHost()}:${container.getMappedPort(6379)}`,
});
await client.connect();
}, 60_000);
afterEach(async () => {
await client.flushAll();
});
afterAll(async () => {
await client.quit();
await container.stop();
});
it('blocks the 6th request within a window', async () => {
for (let i = 0; i < 5; i++) {
expect(await isAllowed(client, 'user-1')).toBe(true);
}
expect(await isAllowed(client, 'user-1')).toBe(false);
});
});
async function isAllowed(client: RedisClientType, key: string): Promise<boolean> {
const count = await client.incr(`rl:${key}`);
if (count === 1) await client.expire(`rl:${key}`, 60);
return count <= 5;
}
// tests/orders.repository.integration.test.ts
import { PostgreSqlContainer, StartedPostgreSqlContainer } from '@testcontainers/postgresql';
import { Pool } from 'pg';
import { runMigrations } from '../src/db/migrate';
import { OrdersRepository } from '../src/db/orders-repository';
let pg: StartedPostgreSqlContainer;
let pool: Pool;
let repo: OrdersRepository;
beforeAll(async () => {
pg = await new PostgreSqlContainer('postgres:16-alpine')
.withDatabase('shop_test')
.withUsername('shop')
.withPassword('shop')
.start();
pool = new Pool({ connectionString: pg.getConnectionUri() });
await runMigrations(pool); // the SAME migrations production runs
repo = new OrdersRepository(pool);
}, 90_000);
beforeEach(async () => {
await pool.query('TRUNCATE orders RESTART IDENTITY CASCADE');
});
afterAll(async () => {
await pool.end();
await pg.stop();
});
it('persists JSONB line items and filters with the @> operator', async () => {
await repo.create({ customerId: 'c1', items: [{ sku: 'SKU-1', qty: 2 }] });
await repo.create({ customerId: 'c2', items: [{ sku: 'SKU-9', qty: 1 }] });
const matches = await repo.findByItemSku('SKU-1'); // uses items @> '[{"sku":"SKU-1"}]'
expect(matches).toHaveLength(1);
expect(matches[0].customerId).toBe('c1');
});
// tests/api.e2e.integration.test.ts
import { DockerComposeEnvironment, StartedDockerComposeEnvironment, Wait } from 'testcontainers';
let environment: StartedDockerComposeEnvironment;
let apiBaseUrl: string;
beforeAll(async () => {
environment = await new DockerComposeEnvironment('.', 'docker-compose.test.yml')
.withWaitStrategy('api-1', Wait.forHttp('/health', 3000).forStatusCode(200))
.withWaitStrategy('postgres-1', Wait.forListeningPorts())
.up(['api', 'postgres']);
const api = environment.getContainer('api-1');
apiBaseUrl = `http://${api.getHost()}:${api.getMappedPort(3000)}`;
}, 120_000);
afterAll(async () => {
await environment.down({ timeout: 10_000 });
});
it('serves orders through the full stack', async () => {
const created = await fetch(`${apiBaseUrl}/orders`, {
method: 'POST',
headers: { 'content-type': 'application/json' },
body: JSON.stringify({ sku: 'SKU-1', qty: 1 }),
});
expect(created.status).toBe(201);
const list = await fetch(`${apiBaseUrl}/orders`);
const orders = (await list.json()) as Array<{ sku: string }>;
expect(orders.map((o) => o.sku)).toContain('SKU-1');
});
// Opt-in reuse keeps the container alive between test runs locally.
// Requires testcontainers.reuse.enable=true in ~/.testcontainers.properties
const pg = await new PostgreSqlContainer('postgres:16-alpine')
.withDatabase('shop_test')
.withReuse()
.start();
// Hand the dynamic URL to the code under test the same way prod config does
process.env.DATABASE_URL = pg.getConnectionUri();
// Copying fixtures and running one-off commands inside a container
const container = await new GenericContainer('postgres:16-alpine')
.withEnvironment({ POSTGRES_PASSWORD: 'shop' })
.withCopyFilesToContainer([
{ source: './tests/fixtures/seed.sql', target: '/docker-entrypoint-initdb.d/seed.sql' },
])
.withExposedPorts(5432)
.start();
const { exitCode, output } = await container.exec(['psql', '-U', 'postgres', '-c', 'SELECT 1']);
expect(exitCode).toBe(0);
expect(output).toContain('1 row');
beforeAll hooks that pull images (60-120 seconds); the first CI run downloads layers.@testcontainers/postgresql, @testcontainers/kafka, @testcontainers/elasticsearch) before reaching for GenericContainer; they encode correct wait strategies and credentials.docker pull postgres:16-alpine) in a cached step to cut suite time."test:integration": "vitest run --config vitest.integration.config.ts") so unit tests stay Docker-free and fast.DATABASE_URL, REDIS_URL); never add test-only config paths to the app.container.logs() streamed to the test reporter when diagnosing startup issues.await sleep(3000) after start() instead of a wait strategy - slow on good days, flaky on loaded CI runners.:latest tags or a different database engine than production.TESTCONTAINERS_RYUK_DISABLED=true) in CI to "fix" a permissions issue, then leaking containers until the runner dies; fix the Docker socket permissions instead.testcontainers or @testcontainers/*, or contains a docker-compose.test.yml.Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.
Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.
Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).
Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).
Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).
This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.
Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.
Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.
Take pramoddutta/docker testcontainers from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npm.
Without those the skill loads but fails at the first command.