Run your tests
- Build images
- Run your image as a container
- Use containers for development
- Run your tests
- Configure CI/CD
- Deploy your app
Prerequisites
Work through the steps to build an image and run it as a containerized application in Use containers for development.
Introduction
Testing is an essential part of modern software development. In combination with 3rd party frameworks or services, Docker helps to test applications without mocks or complicated environment configurations fast and reliably.
Add .NET test project
To test our sample application, we create a standalone test project from a template using the .NET CLI. On your local machine, open a terminal, change the directory to the dotnet-docker
directory and run the following command:
$ cd /path/to/dotnet-docker
$ dotnet new xunit -n myWebApp.Tests -o tests
Next, we’ll update the test project and add the Testcontainers for .NET package that allows us to run tests against Docker resources (PostgreSQL container). Switch to the tests
directory and run the following command:
$ dotnet add package Testcontainers.PostgreSql --version 3.0.0
Add a test
Open the test project in your favorite IDE and replace the contents of UnitTest1
with the following code:
using System;
using System.Net;
using System.Net.Http;
using System.Threading;
using System.Threading.Tasks;
using DotNet.Testcontainers.Builders;
using DotNet.Testcontainers.Containers;
using DotNet.Testcontainers.Networks;
using Testcontainers.PostgreSql;
using Xunit;
public sealed class UnitTest1 : IAsyncLifetime, IDisposable
{
private const ushort HttpPort = 80;
private readonly CancellationTokenSource _cts = new(TimeSpan.FromMinutes(1));
private readonly INetwork _network;
private readonly IContainer _dbContainer;
private readonly IContainer _appContainer;
public UnitTest1()
{
_network = new NetworkBuilder()
.Build();
_dbContainer = new PostgreSqlBuilder()
.WithImage("postgres")
.WithNetwork(_network)
.WithNetworkAliases("db")
.WithVolumeMount("postgres-data", "/var/lib/postgresql/data")
.Build();
_appContainer = new ContainerBuilder()
.WithImage("dotnet-docker")
.WithNetwork(_network)
.WithPortBinding(HttpPort, true)
.WithWaitStrategy(Wait.ForUnixContainer().UntilHttpRequestIsSucceeded(request => request.ForPath("/")))
.Build();
}
public async Task InitializeAsync()
{
await _network.CreateAsync(_cts.Token)
.ConfigureAwait(false);
await _dbContainer.StartAsync(_cts.Token)
.ConfigureAwait(false);
await _appContainer.StartAsync(_cts.Token)
.ConfigureAwait(false);
}
public Task DisposeAsync()
{
return Task.CompletedTask;
}
public void Dispose()
{
_cts.Dispose();
}
[Fact]
public async Task Test1()
{
using var httpClient = new HttpClient();
httpClient.BaseAddress = new UriBuilder("http", _appContainer.Hostname, _appContainer.GetMappedPublicPort(HttpPort)).Uri;
var httpResponseMessage = await httpClient.GetAsync(string.Empty)
.ConfigureAwait(false);
var body = await httpResponseMessage.Content.ReadAsStringAsync()
.ConfigureAwait(false);
Assert.Equal(HttpStatusCode.OK, httpResponseMessage.StatusCode);
Assert.Contains("Welcome", body);
}
}
The test class picks up the configurations and lessons we learned in the previous steps. It connects our application and database through a custom Docker network and runs an HTTP request against our application. As you can see, running containerized tests allows us to test applications without mocks or complicated environment configurations. The tests run on any Docker-API compatible environments including CI.
Next steps
In the next module, we’ll take a look at how to set up a CI/CD pipeline using GitHub Actions. See:
Feedback
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the Docker Docs GitHub repository. Alternatively, create a PR to suggest updates.