FakeItEasy | The easy mocking library for .NET | Mock library

OK, I was able to reproduce your error message by defining ignored as:

Updated after getting new code and stack trace. Original answer left below

I think it's a bug.

Boring explanation:

Strict and Wrapping each add rules to the front of the faked object's rules list. The rules apply to all incoming calls. The first rule found that matches a call is triggered. So in your configuration, Wrapping is added making the Fake attempt to forward all calls to the wrapped object. Then Strict, so now the Fake will reject all calls.

You'd then expect

First, you should implement method that reads from file, which exists in the projects of unit test. So, if there is no file .json that you can read from you won;t be able to GetSection at all. So add file there then apply:

Is there a way to insure that the module object will be a fakeiteasy fake when I write my unit test?

No, it's not possible, at least not with the current shape of your code. FakeItEasy can't intercept instance creation using new.

If you want to fake something, it has to be provided somehow to the system under test. The SUT can't create it itself.

I cannot provide a searchmodule instance as a parameter of the function Search, nor as a constructor parameter of the class SearchEngine

Could you inject a factory instead? Something like this:

According to my reading of the docs, if you're using a non-EventHandler event, you need to use Raise.FreeForm.With:

"Method group" is a concept that exists only in the language's syntax, there is no runtime type that corresponds to a method group.

Before I answer the question, you can just do this at callsite:

AutoFixture can only build upon the testing framework only as much as it allows itself to be extended. In xUnit 2 each provided DataAttribute is considered, a distinct provider of arguments for the test, which is why they are isolated during runtime.

The recommended option here is to create a data attribute that will apply both AutoMoq and the AutoMapper customization.

You can achieve this by using a CompositeCustomization and then using it in a custom AutoDataAttribute implementation.

In your assertion, you create a new instance of CreateOwnerRequest. Obviously, this isn't the same instance that is actually used in the controller action, so it isn't considered equal, and the assertion fail.

You could override Equals on CreateOwnerRequest so that they are considered equal, but it's probably not a good idea, since you would do it only in order to satisfy the assertion.

A better approach is to use argument constraints to specify a condition that the argument must match:

Your test is perfectly good, as far as it goes. If you run it, it'll tell you that ProtectedDo was not called, which is accurate. Because Do_Override is virtual, FakeItEasy intercepts the call. (The protectedness doesn't affect things in this case.)

If you don't want Do_Override to be intercepted by FakeItEasy, you should configure the Fake to call the base method instead of handling the call itself: