Testcontainers for .NET

Testy integracyjne w .NET przeciwko prawdziwym kontenerom Docker, na aktualnych API 4.x

Autor: testcontainers · testcontainers/claude-skills

Działa po konfiguracji ★ 7.6/10

Testcontainers for .NET — Testy integracyjne w .NET przeciwko prawdziwym kontenerom Docker, na aktualnych API 4.x

Co robi ten skill

Referencja do pisania Testcontainers for .NET integration tests: module selection, builder configuration, wait strategies, container networking, volume and file mapping, cleanup via Ryuk, and worked xUnit, NUnit and MSTest examples for Postgres, Redis, SQL Server with EF Core, Kafka and multi-container stacks. Uruchamia się, gdy potrzebujesz real database or message queue in a .NET test instead of a mock, or when Testcontainers tests are flaky in CI.

Raport z testu

Nothing here could be compiled or run: this machine has no .NET SDK and no Docker or Podman, and Docker is a hard prerequisite for every example in the file, so the output score is left at no-measured-difference rather than guessed at. What I could check, I checked against the library's own source at version 4.13.0: every API the skill uses exists, the Ryuk image tag it names matches the one hardcoded in ResourceReaper.cs, and the constructor pattern it teaches is the one that is still current — the parameterless PostgreSqlBuilder() that most blog posts and a from-memory answer still reach for is marked [Obsolete] "will be removed" in the shipped code. Its own claim of 65+ modules is a shade high, with 64 module projects in the repository, and one Kafka example pins a different image than the library default. Install is clean from a bare HOME and the file is a genuinely well-organised reference, but you need Docker running before any of it does anything.

Testowano: 2026-07-30 · Claude Code 2.x (agent harness)

Instalacja

git clone https://github.com/testcontainers/claude-skills.git
mkdir -p ~/.claude/skills
cd claude-skills && cp -r plugins/testcontainers/skills/testcontainers-dotnet ~/.claude/skills/testcontainers-dotnet

Komendy i przykładowe prompty

/testcontainers-dotnetTesty integracyjne w .NET przeciwko prawdziwym kontenerom Docker, na aktualnych API 4.x

Skille uruchamiają się na zwykłe polecenia — bez komend do zapamiętania. Po instalacji aktywują go prompty takie jak te (po angielsku):

Write an xUnit integration test against a real Postgres container in Docker
Our Testcontainers tests are flaky in CI, the container isn't ready in time
How do I share one SQL Server container across an xUnit test class?

Pełny raport →