testcontainers-dotnet

Integration tests with Docker containers use Testcontainers to spin up isolated services like PostgreSQL or RabbitMQ during test execution. Testcontainers manages container lifecycle automatically, letting you test against real dependencies without manual setup. This approach ensures tests are reproducible and don't interfere with each other.

Yes. Testcontainers integrates with xUnit v3 through IAsyncLifetime, ClassFixture, and AssemblyFixture patterns, fully compatible with the Microsoft Testing Platform. This combination provides reliable container coordination across test classes and assemblies with native async support.

Sealed client wrappers let you abstract sealed types behind testable interfaces. Combined with Moq patterns like MockRepository and handler extraction, you can inject fake implementations during tests without modifying external library code.

Testcontainers for .NET supports PostgreSQL, RabbitMQ, Elasticsearch, and MinIO as pre-built fixtures. Each container runs in isolation and shuts down automatically after tests complete, ensuring clean test environments and preventing resource leaks.

Yes. Testcontainers requires Docker access to spawn and manage containers. You must have Docker installed and running on your development machine or CI/CD environment before executing integration tests.

The Microsoft Testing Platform provides native code coverage collection that works alongside Testcontainers and xUnit v3. Configure coverage collection in your test project, and metrics are gathered during test execution without additional tooling.