ExpressionToCode VS Moq

(Source: I needed to hack a detection for this for my expression-tree-to-csharp decompiler, here: https://github.com/EamonNerbonne/ExpressionToCode/pull/196)

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.

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

This looks like the kind of thing Moq could handle with LINQ to Mocks.

Full code can be found here. More on Moq can be found here.

Moq

> edit: one more qualm, the Mockito equivalent for C#, NSubstitute, cannot mock a concrete class, only an interface.

I've never heard of NSubstitute (that doesn't mean it's bad), but most places I've worked at typically use Moq (https://github.com/moq/moq4) which does support interfaces and classes.