docs: Add "Run your tests" section to .NET (#16244)

* docs: Add "Run your tests" section to .NET

* fix: Add "Run your tests" to toc.yaml
This commit is contained in:
Andre Hofmeister 2023-01-20 23:20:28 +01:00 committed by GitHub
parent 67ff95b75a
commit 3affff66e4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 134 additions and 6 deletions

View File

@ -125,6 +125,8 @@ guides:
path: /language/dotnet/run-containers/
- title: "Develop your app"
path: /language/dotnet/develop/
- title: "Run your tests"
path: /language/dotnet/run-tests/
- title: "Configure CI/CD"
path: /language/dotnet/configure-ci-cd/
- title: "Deploy your app"

View File

@ -4,7 +4,7 @@ keywords: .net, CI/CD, local, development
description: Learn how to Configure CI/CD for your application
---
{% include_relative nav.html selected="4" %}
{% include_relative nav.html selected="5" %}
## Get started with GitHub Actions

View File

@ -4,7 +4,7 @@ keywords: deploy, ACI, ECS, .net, local, development
description: Learn how to deploy your application
---
{% include_relative nav.html selected="5" %}
{% include_relative nav.html selected="6" %}
{% include deploy.md %}

View File

@ -451,9 +451,9 @@ Now lets test our application. Using a web browser, access `http://localhost:
## Next steps
In the next module, well take a look at how to set up a CI/CD pipeline using GitHub Actions. See:
In the next module, well take a look at how to write containerized tests in Docker. See:
[Configure CI/CD](configure-ci-cd.md){: .button .primary-btn}
[Run your tests](run-tests.md){: .button .primary-btn}
## Feedback

View File

@ -2,6 +2,7 @@
<li {% if include.selected=="1"%}class="active"{% endif %}><a href="/language/dotnet/build-images/">Build images</a></li>
<li {% if include.selected=="2"%}class="active"{% endif %}><a href="/language/dotnet/run-containers/">Run your image as a container</a></li>
<li {% if include.selected=="3"%}class="active"{% endif %}><a href="/language/dotnet/develop/">Use containers for development</a></li>
<li {% if include.selected=="4"%}class="active"{% endif %}><a href="/language/dotnet/configure-ci-cd/">Configure CI/CD</a></li>
<li {% if include.selected=="5"%}class="active"{% endif %}><a href="/language/dotnet/deploy/">Deploy your app</a></li>
<li {% if include.selected=="4"%}class="active"{% endif %}><a href="/language/dotnet/run-tests/">Run your tests</a></li>
<li {% if include.selected=="5"%}class="active"{% endif %}><a href="/language/dotnet/configure-ci-cd/">Configure CI/CD</a></li>
<li {% if include.selected=="6"%}class="active"{% endif %}><a href="/language/dotnet/deploy/">Deploy your app</a></li>
</ul>

View File

@ -0,0 +1,125 @@
---
title: "Run your tests"
keywords: .NET, build, test
description: How to build and run your tests
---
{% include_relative nav.html selected="4" %}
## Prerequisites
Work through the steps to build an image and run it as a containerized application in [Use containers for development](develop.md).
## 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:
```console
$ 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. Switch to the `tests` directory and run the following command:
```console
$ dotnet add package Testcontainers
```
## Add a test
Open the test project in your favorite IDE and replace the contents of `UnitTest1` with the following code:
```c#
using System.Net;
using DotNet.Testcontainers.Builders;
using DotNet.Testcontainers.Containers;
using DotNet.Testcontainers.Networks;
public sealed class UnitTest1 : IAsyncLifetime, IDisposable
{
private const ushort HttpPort = 80;
private readonly CancellationTokenSource _cts = new(TimeSpan.FromMinutes(1));
private readonly IDockerNetwork _network;
private readonly IDockerContainer _dbContainer;
private readonly IDockerContainer _appContainer;
public UnitTest1()
{
_network = new TestcontainersNetworkBuilder()
.WithName(Guid.NewGuid().ToString("D"))
.Build();
_dbContainer = new TestcontainersBuilder<TestcontainersContainer>()
.WithImage("postgres")
.WithNetwork(_network)
.WithNetworkAliases("db")
.WithVolumeMount("postgres-data", "/var/lib/postgresql/data")
.Build();
_appContainer = new TestcontainersBuilder<TestcontainersContainer>()
.WithImage("dotnet-docker")
.WithNetwork(_network)
.WithPortBinding(HttpPort, true)
.WithWaitStrategy(Wait.ForUnixContainer().UntilPortIsAvailable(HttpPort))
.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, well take a look at how to set up a CI/CD pipeline using GitHub Actions. See:
[Configure CI/CD](configure-ci-cd.md){: .button .primary-btn}
## Feedback
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.