AutoMoq | Auto mocking provider for Moq | Mock library

I created some unit tests on an existing project. I am using AutoMoq to inject data into some of the tests. Upon running the test, it complains of recursion error. I solved the error using the below code:

I am using AutoFixture AutoMoq and it's greatly simplifies the mock for all interface used in class and initialize it.

Though I noticed the constructor code is partially covered, can we modify AutoMoqDataAttribute so that constructor ArgumentNullException can also be covered?

I'm using AutoFixture in my unit tests. The SUT is using AutoMapper. During execution of the unit test, I noticed that IMapper (interface of AutoMapper) was getting mocked by AutoFixture and thus disregarding any mapping profiles I have in my code.

So I wrote a customization to be able to pass in an IMapper instance so that AutoFixture will not mock this interface. But now it looks like that AutoFixture won't mock any other interfaces as well. This used to work before I introduced the AutoMapper customization.

Let's say that I have the following code example:

In a solution, I have 600 unit tests splitted in various libraries, and 450 of them are present in a single library. When running the tests on that specific library on my computer using Visual Studio (last version), everything goes well. But, on our build server, some tests never ends using the dotnet.exe test command.

I am using AutoFixture with AutoMoq to mock my dependencies in a unit test like this

I am using Moq and AutoFixture.

Given the following interfaces:

I am trying to unit test code that uses SearchClient.SearchAsync() method. I am using AutoFixture.AutoMoq nuget package.

Here is what I tried:

My tests use Moq and AutoFixture, and often they are very verbose because they have many mock Setup() calls to configure mocks to return values created by AutoFixture. To make the tests easier to read and maintain I am trying to use AutoMoqCustomization with the ConfigureMembers feature to avoid unnecessary Setup() calls.

Mostly this is working as expected, however I have some interfaces with generic functions (AutoMapper mostly) that the AutoMoqCustomization does not seem to handle. Instead of returning an instance of the type from AutoFixture I receive a mocked instance.

I can achieve the behavior that I want by including a Setup() call for the generic function, but my goal was to remove as many of these Setup calls as possible.

I have set up the example below to reproduce the problem (in practice I am using AutoFixture to inject an IMapper instance via the constructor of another object, and that object makes the call to the IMapper interface, but that is not necessary to see the problematic behavior).

What I expect is for the call to sut.Map() to work like the call to sut.Map(), returning the instance of object frozen in the fixture. Instead in variable retB I see an instance of ObjectProxy.