Skill

test-infrastructure

Test infrastructure: Testcontainers with real PostgreSQL (60s timeout), parallel test isolation (per-worker schema), flaky test quarantine, test data seeding patterns, ephemeral test databases, CI database setup. Use when setting up database testing, managing test isolation, improving CI test reliability.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milligan

Tool Access

This skill is limited to using the following tools:

ReadGrepGlob

Preview

- Setting up database tests with real PostgreSQL (not mocks)

Supporting Assets

references/ci-optimization.mdreferences/flaky-test-management.mdreferences/test-environments.mdscripts/detect-flaky-tests.sh

SKILL.md

Similar Skills

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

156.2k

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

156.2k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitFeb 23, 2026

Actions

View Source View Plugin View on GitHub View README

test-infrastructure

Core principles

Real database over mocks — SQLite for tests when you use PostgreSQL in prod = false confidence

Parallel isolation via schemas — each worker gets its own schema, no shared state

Deterministic test data — use factories, not shared fixtures that accumulate side effects

Flaky tests: quarantine immediately — don't let them degrade CI trust

Fast teardown — truncate tables, not DROP/CREATE (seconds vs minutes)

References available

references/testcontainers-setup.md — PostgreSqlContainer config, 60s startup timeout, migrate on start

references/per-worker-isolation.md — vitest thread pool, globalSetup schema creation, search_path config

references/test-data-seeding.md — factory pattern with beforeEach, seedStandardData, truncateAll

references/flaky-quarantine.md — it.skip + ticket process, 1-week SLA, fix vs delete decision

references/ci-database-setup.md — GitHub Actions service containers, health checks, schema init steps

Test Infrastructure

When to use

Setting up database tests with real PostgreSQL (not mocks)
Isolating tests that run in parallel
Managing test data with factories and seeds
Handling flaky tests in CI
Testcontainers for integration tests

Core principles

Real database over mocks — SQLite for tests when you use PostgreSQL in prod = false confidence
Parallel isolation via schemas — each worker gets its own schema, no shared state
Deterministic test data — use factories, not shared fixtures that accumulate side effects
Flaky tests: quarantine immediately — don't let them degrade CI trust
Fast teardown — truncate tables, not DROP/CREATE (seconds vs minutes)

References available

references/testcontainers-setup.md — PostgreSqlContainer config, 60s startup timeout, migrate on start
references/per-worker-isolation.md — vitest thread pool, globalSetup schema creation, search_path config
references/test-data-seeding.md — factory pattern with beforeEach, seedStandardData, truncateAll
references/flaky-quarantine.md — it.skip + ticket process, 1-week SLA, fix vs delete decision
references/ci-database-setup.md — GitHub Actions service containers, health checks, schema init steps