README

Intro

This is a sample repo for setting up API testing in .NET.

It includes:

• Demonstrating mocking services
• Getting application logs into test output by using xUnit's ITestOutputHelper
• Using Testcontainers to run tests against a real SQL Server

The project contains 2 different APIs and 2 different test projects

• NetWebApi and Test.NetWebApi using the regular Microsoft provided dependency injection container
• NetWebApi.LightInject and Test.NetWebApi.LightInject using the LightInject dependency injection container

Setup

Running the API

1. Run the SQL Server compose file:

docker-compose up -d

2. Build and run API through Visual Studio, Rider or command line.

Running the tests

1. Make sure you have Docker running.

2. Run the tests in either Test.NetWebApi or Test.NetWebApi.LightInject

Resources

• Docs: Integration tests in ASP.NET Core
• David Fowler's gist
• What is Testcontainers, and why should you use it?

Notes

EF Core in-memory provider

The EF Core in-memory provider is NOT recommended for use in integration testing:

EF Core also comes with an in-memory provider. Although this provider was originally designed to support internal testing of EF Core itself, some developers use it as a database fake when testing EF Core applications. Doing so is highly discouraged.

Source: https://docs.microsoft.com/en-us/ef/core/testing/choosing-a-testing-strategy#in-memory-as-a-database-fake