Why use Testcontainers instead of InMemory EF Core database?

InMemory does not execute raw SQL, foreign keys, transactions, or concurrency tokens. Testcontainers boots real SQL Server in Docker for 100% fidelity: Testcontainers for ASP.NET Core.

How do I test an ASP.NET Core API pipeline?

Use WebApplicationFactory to send real HTTP requests through middleware: ASP.NET Core integration tests with WebApplicationFactory.

Blog topic

Integration and API Testing for ASP.NET Core

Real database and service testing for ASP.NET Core — Testcontainers for SQL Server and Redis, and WebApplicationFactory integration tests.

Fast, reliable integration testing without mocking your database away. Start with Testcontainers for ASP.NET Core or WebApplicationFactory integration testing.

Introduction

This page is the article map for integration and automated testing in ASP.NET Core applications.

You want…	Open
Real SQL & Redis with Testcontainers	Testcontainers for ASP.NET Core
Pipeline HTTP tests with WebApplicationFactory	ASP.NET Core integration tests

Integration tests should test real database behavior, transactions, and HTTP pipelines rather than in-memory mocks.

Related: DevOps & CI/CD · EF Core · API Design

Quick answers

Why use Testcontainers instead of InMemory EF Core database?: InMemory does not execute raw SQL, foreign keys, transactions, or concurrency tokens. Testcontainers boots real SQL Server in Docker for 100% fidelity: Testcontainers for ASP.NET Core.
How do I test an ASP.NET Core API pipeline?: Use WebApplicationFactory to send real HTTP requests through middleware: ASP.NET Core integration tests with WebApplicationFactory.

All Testing articles

October 1, 20269 min read

Testcontainers for ASP.NET Core: Real SQL and Redis Testing

ASP.NET Core integration tests with Testcontainers — real SQL or Postgres and Redis beside WebApplicationFactory. Extends WebApplicationFactory; not Angular E2E.

September 18, 20263 min read

ASP.NET Core Integration Tests with WebApplicationFactory

Test an ASP.NET Core API through its real pipeline with WebApplicationFactory: replace the database, send HTTP, and check status codes instead of calling controllers as classes.