NBuilder VS Moq

Would it be easier to avoid getting into those details if you could design a system to generate the details for you? There's a library called NBuilder(https://www.nuget.org/packages/NBuilder/6.1.0) that can generate lists of objects populated by junk data for use with tests. Can you use that, or something like it, to populate all the stuff that you shouldn't be spending your time on?

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.)

Moq tutorial