Moq VS AutoFixture

8. Moq

In terms of mocking there are several frameworks you can use, but I've mainly relied on Moq and NSubstitute. Within this demo, I'm going to use NSubstitute as I've found it a little easier to use.

Or you just run into bullshit like https://github.com/Moq/moq4/issues/173

Now to the real benefit of DI: If you are testing a method in your application that calls the ReservationRepository.GetReservation() method, you can use a library like Moq to simply "mock" a class that uses the IReservationRepository interface and define the return result of the GetReservation() method. Pass the mocked class into the constructor of the class you are testing.

MOQ https://github.com/moq/moq4

Moq

Both projects use similar testing infrastructure. I write unit tests in C# using XUnit.net. I frequently use mock objects in testing, and MOQ is my tool of choice. I utilize continuous testing and coverage analysis through Rider. I do not have specific objectives for code coverage. When writing complicated algorithms, I frequently shoot for 100% coverage of the algorithm. I test simple properties inconsistently, and frequently do not test guard clauses.

🔗 Moq documentation | GitHub

But the reality is that I don't really write my tests with it. Toss on the MSTest attributes as needed of course. But all the testing code itself is FluentAssertions with a bit of Moq. (Though I find rarely need to use Moq/mocking anymore -- scandalous, I know.)

His AutoFixture C# NuGet takes away so much pain from unit test maintenance. It does have a learning curve.

https://github.com/AutoFixture/AutoFixture

Yes, it does feel like some of the "standard stuff" in other more nuanced languages are missing (especially miss AutoFixture ngl). Some of those are a conscious decison by the golang team for example.

Our first test is very easy, I like to name my tests as MethodName_GivenCondition_ShouldExpectedResult to follow the pattern, I have added GetById_GivenRecordDoesNotExist_ShouldReturnNull and I am going to leavarage excellent AutoFixture to get a new Guid as parameter. For this test we don't need arrange part, we would skip to the act and then assert. For Assertion I am going to use FluentAssertions. For this test we need to assert the returned result is null.

The next test to talk about, is that if this was a bank, we would have multiple customers, who can hold multiple accounts that we need to calculate the interest for. You could manually construct these objects if you want, but I'm going to use a package called AutoFixture to make life easier.

AutoFixture is an amazing library that simplifies the process of creating test data in .NET. If for some reason you don't use this fantastic tool, it's time to consider it. Today, I'm going to share some tips for using AutoFixture that will be beneficial for developers of all skill levels. Let's get started!

AutoFixture

Ensuring that your test is still readable and not bloated by the setup of those variables may be quite a challenge but hopefully no more with AutoFixture, let's see how!

One neat library for creating and generating test data is AutoFixture.  The creators describe it as follows:

First time I heard of Bogus, looks interesting, been using AutoFixture for those will definitely take a look at it.