Question 1

How to set up a fake method to return a value in FakeItEasy?

Accepted Answer

Use A.CallTo with a lambda expression and .Returns, as shown in the example: A.CallTo(() => shop.GetTopSellingCandy()).Returns(lollipop). This configures the fake to return the specified object when the method is called.

Question 2

FakeItEasy vs Moq which one should I use?

Accepted Answer

FakeItEasy is better for developers prioritizing ease of use and clean syntax, as it guides you with a fluent interface. Moq offers more advanced features and a larger ecosystem, so choose based on your need for simplicity versus power.

Question 3

Can FakeItEasy mock static methods or sealed classes?

Accepted Answer

No, FakeItEasy primarily works with interfaces and virtual members due to its dynamic proxy approach. Static methods and non-virtual members in sealed classes are generally not mockable without workarounds like wrapping.

Question 4

How to verify a method was called multiple times with FakeItEasy?

Accepted Answer

Use A.CallTo(...).MustHaveHappened() with parameters, such as A.CallTo(() => method()).MustHaveHappened(2, Times.Exactly) to check for exact call counts, leveraging the fluent interface for precise assertions.

Question 5

Is FakeItEasy compatible with .NET Core and newer versions?

Accepted Answer

Yes, FakeItEasy supports .NET Core and modern .NET versions, including .NET 8.0 and 10.0 as per the NuGet targets, ensuring it works with contemporary .NET applications without issues.

Question 6

How to handle events when using FakeItEasy fakes?

Accepted Answer

FakeItEasy provides methods like A.CallTo(...).Raises(...) to simulate event firing on fakes, but it may require additional setup compared to basic method calls, as detailed in the documentation.

FakeItEasy

What is FakeItEasy?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions