Unit testing your code

Jon P Smith edited this page May 23, 2018 · 3 revisions

Typically you don't use dependency injection in unit testing, so you need a way to get the information you need. I have produced a couple of extension methods to allow you to set up the system and return a UnitTestData instance that contains the IWrappedAutoMapperConfig instance you need to create an instance of the CrudServices or CrudServicesAsync.

NOTE: This would also be useful in serverless applications where you only want to register one or maybe two DTOs.

There are plenty of unit tests to look at, but here is a simple unit test using the UnitTestSetup extension method.

public void TestProjectBookTitleSingleOk()
    var options = SqliteInMemory.CreateOptions<EfCoreContext>();
    using (var context = new EfCoreContext(options))

        var utData = context.SetupSingleDtoAndEntities<BookTitle>();
        var service = new CrudServices(context, utData.Wrapped);

        var dto = service.ReadSingle<BookTitle>(1);


If you need to register more than one DTO then there is another extension that can do that. e.g.

var utData = context.SetupSingleDtoAndEntities<BookTitle>();
//... etc.

You should be aware that I use static ConcurrentDictionarys to cache many things. So, if a test works when you run all the tests, but fails if you run the test on its own, then it is most likely because you have not set up the correct DTO/DbContext in the test that fails on its own.

NOTE: I also would point you to my EfCore.TestSupport library which contains a range of tools for unit testing applications that use EF Core.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.