BunsenBurner.DependencyInjection 6.2.4

Bunsen Burner Dependency Injection

This provides extension methods to test that a standard DI container is configured correctly.

Getting Started

To use this library, simply include BunsenBurner.DependencyInjection.dll in your projector grab it from NuGet, and add this to the top of each test .cs file that needs it:

using static BunsenBurner.DependencyInjection.Aaa;

or

using static BunsenBurner.DependencyInjection.Bdd;

What?

The standard Dependency Injection container in dotnet is not typesafe and requires runtime verification to ensure that its configured correctly.

This is a very simple test that builds all services that match a predicate.

There are default predicates that operate on an assembly(s). This will in most cases do the job.

How to use

To start using it import the syntax that your test project is using.

using static BunsenBurner.DependencyInjection.Aaa;

public static class DITests
{
    [Fact(DisplayName = "All services are resolvable in the project assembly")]
    public static async Task Case1() =>
        await new Startup()
            .ArrangeData()
            .ActAndAssertServicesAreConfigured(
                // convert the data to a service collection
                startup => startup.ConfigureServices(new ServiceCollection()),
                // now build anything found in the provided assemblies
                typeof(Startup).Assembly);
}

For more information on the added arrange functions check out the code and the tests.