How to link Autofac to UnitTesting

Question

Within my Web API I have linked Autofac as IoC container, and I do it like this:

Domain level

public class Autofac
{
    protected ContainerBuilder Builder { get; set; }

    public Autofac()
    {
        this.Builder = new ContainerBuilder();
    }

    public virtual IContainer Register()
    {
        // Register dependencies

        SetUpRegistration(this.Builder);

        // Build registration.
        var container = this.Builder.Build();

        // End
        return container;
    }   

    private static void SetUpRegistration(ContainerBuilder builder)
    {
        // === DATALAYER === //

        // MyRepository
        builder.RegisterType<MyRepository>()
            .As<IMyRepository>()
            .InstancePerLifetimeScope();

        // === DOMAIN === //

        // MyManager
        builder.RegisterType<MyManager>()
            .As<IMyManager>()
            .InstancePerLifetimeScope();
    }
}

Web API

public class Autofac : Domain.IoC.Autofac
{
    public IContainer Register(HttpConfiguration config)
    {
        // Register your Web API controllers.
        base.Builder.RegisterApiControllers(Assembly.GetExecutingAssembly());

        // OPTIONAL: Register the Autofac filter provider.
        base.Builder.RegisterWebApiFilterProvider(GlobalConfiguration.Configuration);

        // Complete registration and get container instance.
        var container = base.Register();

        // Set the dependency resolver to be Autofac.
        config.DependencyResolver = new AutofacWebApiDependencyResolver(container);

        // Done.
        return container;
    }
}

As you see it inherits from the base class from Domain and sets up Web API specific config.

Usage

protected void Application_Start()
{
    AreaRegistration.RegisterAllAreas();
    GlobalConfiguration.Configure(WebApiConfig.Register);
    FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters);
    RouteConfig.RegisterRoutes(RouteTable.Routes);
    BundleConfig.RegisterBundles(BundleTable.Bundles);

    new IoC.Autofac().Register(GlobalConfiguration.Configuration);
}

Which is at global.asax, as you know.

The question

This works fine for Web API, but I haven't got a clue what I need to do to register all this within a UnitTest project context.

The idea is that I would create a similar implementation to the Autofac class at Web API level, but than with mocks (completely ignoring the base class from Domain).

Any pointers?

Answer 1

Personally I never see the need (and I struggle to comprehend how viable or helpful it would be) to setup my IoC container directly within a unit test. As a unit test is used to test a logical piece of code that can be quickly built, easily ran and doesn't require much (I'd advocate no) tear-down. It should not require all of your application to be be setup for the test to run.

Remember that your unit test is simply testing the flow of data through the system i.e that your DomainManager is actually going to call a IRepository when you expect that it should. Then you would have separate test classes for all your repositories to determine that they would correctly add to the database etc.

I'm not sure how you use the DBContext class but as an example of a wrapper this is what it would sort of look like.

interface IDBSetWrapper
{
    object Add(object entity);
}

interface IDBContextWrapper
{
    ...
    IDBSet Set(Type entityType);
    ...
}

class DBContextWrapper : IDBContextWrapper
{
    private readonly DBContext context;

    public DBContextWrapper()
    {
        context = new DBContext();
    }

    ...

    public IDBSet Set(Type entityType)
    {
        var dbSet = context.Set(entityType);
        return new DBSetWrapper(dbSet);
    }

    ...
}

It's not much but I hope that it demonstrates what I mean about a thin wrapper. Basically the wrapper is the DBContext and will contain an instance of it within the class, the actual DBContext will be called when you request the wrapper to do anything. I have shown what would happen when returning another object (in this case a DBSet), this will also be wrapped in a separate object with an interface. This is so that you can mock the returns from this class easily.

You can add this new wrapper into your IoC a little better now as it provides an interface.

One thing to note is that you won't be able to and probably wouldn't wish to test the wrapper class, there would be very little point as I see it. But previously I've seen colleagues do an integration test on these sort of classes.