Documentation on Dotnet Test Util

Assertions & Attributes

Mon, 01 Jan 0001 00:00:00 +0000

This page covers CustomAssert and the environment-aware test attributes.

CustomAssert

CustomAssert is a static class with the null/empty assertions that come up most often, so you don’t have to spell out Assert.True(collection is null || !collection.Any()) every time. Each method throws the same exception type as a failing Assert, so failures read exactly like normal xUnit failures.

Method	Passes when
`NullOrEmpty(IEnumerable?)`	The collection is `null` or has no elements
`NotNullOrEmpty(IEnumerable?)`	The collection is not `null` and has at least one element
`NullOrEmpty(string?)`	The string is `null` or empty
`NotNullOrEmpty(string?)`	The string is not `null` and not empty
`NullOrWhiteSpace(string?)`	The string is `null`, empty, or only white space
`NotNullOrWhiteSpace(string?)`	The string has at least one non-white-space character

CustomAssert.NullOrEmpty(Array.Empty<int>()); // passes
CustomAssert.NullOrEmpty((IEnumerable?)null); // passes
CustomAssert.NotNullOrEmpty(new[] { 1, 2, 3 }); // passes

CustomAssert.NullOrWhiteSpace(" "); // passes
CustomAssert.NotNullOrWhiteSpace("value"); // passes

The collection overloads treat null and empty the same way, so a null reference never trips up a NullOrEmpty check.

Fakes

Mon, 01 Jan 0001 00:00:00 +0000

This page covers the in-memory test doubles: FakeRepository<T, TKey>, AsyncFakeRepository<T, TKey> and FakeScheduler.

FakeRepository<T, TKey>

FakeRepository<T, TKey> is an in-memory implementation of IRepository<T, TKey> (from ArturRios.Data.Relational.Core). It stores entities in a backing list so you can exercise services that depend on a repository without touching a database. T must derive from ArturRios.Data.Relational.Core.Entities.Entity<TKey>, and TKey is the entity’s key type (long, int, Guid, string, …). Every method except Query() returns a DataOutput<...>, with the outcomes EfRepository<T, TKey> produces, so a test that passes against the fake passes for the reason it would in production: a lookup that finds nothing succeeds with no data, and an update or delete that would affect no row fails with RelationalErrors.ConcurrencyMessage and changes nothing.

Web API Testing

Mon, 01 Jan 0001 00:00:00 +0000

WebApiTest<T> is a base class for functional web API tests. It hosts your API in memory with WebApplicationFactory<T> and exposes an HttpGateway plus helpers for authenticating and authorizing requests.

Getting started

Derive from WebApiTest<T>, where T is the entry point of the API under test (typically its Program class), and pass the environment to run as:

public class ProductsApiTests : WebApiTest<Program>
{
 private static readonly Credentials Credentials = new("user@test.com", "secret123");

 public ProductsApiTests() : base(EnvironmentType.Local) { }

 [Fact]
 public async Task Rejects_anonymous_requests()
 {
 var response = await Gateway.GetAsync<DataOutput<ProductOutput>>("/products/1");

 Assert.Equal(HttpStatusCode.Unauthorized, response.StatusCode);
 }

 [Fact]
 public async Task Creates_a_product()
 {
 await AuthenticateAndAuthorizeAsync(Credentials, "/auth");

 var response = await Gateway.PostAsync<DataOutput<ProductOutput>>("/products", new { Name = "Widget" });

 Assert.Equal(HttpStatusCode.OK, response.StatusCode);
 }
}

The constructor sets ASPNETCORE_ENVIRONMENT to the given environment (lower-cased), starts the in-memory host, and creates the gateway against it.