Fine Code Coverage
Moq
| Fine Code Coverage | Moq | |
|---|---|---|
| 1 | 26 | |
| 485 | 5,215 | |
| - | - | |
| 9.4 | 6.6 | |
| about 1 month ago | 10 months ago | |
| C# | C# | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Fine Code Coverage
-
C# development tools
If you start writing unit tests, I highly recommend Fine Code Coverage to see what percentage of your code has been reached by the existing unit tests: https://github.com/FortuneN/FineCodeCoverage
Moq
-
Setting up a simple testing project with C#
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.
-
What if writing tests was a joyful experience
Or you just run into bullshit like https://github.com/Moq/moq4/issues/173
- Moq.NET Mocking framework [C#]
-
Dependency injection
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.
-
Usefully links for DotNet Backend Developers
MOQ https://github.com/moq/moq4
-
I need a C# crash course for experienced developers
Moq
-
A Tale of 2 Codebases (Part 2 of 4): Testability
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 vs NSubstitute: syntax cheat sheet
🔗 Moq documentation | GitHub
-
What's your go-to unit testing tool?
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.)
-
How YOU can Learn Mock testing in .NET Core and C# with Moq
Moq tutorial
What are some alternatives?
SpecFlow - #1 .NET BDD Framework. SpecFlow automates your testing & works with your existing code. Find Bugs before they happen. Behavior Driven Development helps developers, testers, and business representatives to get a better understanding of their collaboration
FakeItEasy - The easy mocking library for .NET
MSTest - MSTest framework and adapter
NSubstitute - A friendly substitute for .NET mocking libraries.
NUnit - NUnit Framework
Bogus - :card_index: A simple fake data generator for C#, F#, and VB.NET. Based on and ported from the famed faker.js.
ReportGenerator - ReportGenerator converts coverage reports generated by coverlet, OpenCover, dotCover, Visual Studio, NCover, Cobertura, JaCoCo, Clover, gcov or lcov into human readable reports in various formats.
AutoMoq - Auto mocking provider for Moq.
Expecto - A smooth testing lib for F#. APIs made for humans! Strong testing methodologies for everyone!
AutoFixture - AutoFixture is an open source library for .NET designed to minimize the 'Arrange' phase of your unit tests in order to maximize maintainability. Its primary goal is to allow developers to focus on what is being tested rather than how to setup the test scenario, by making it easier to create object graphs containing test data.
CheckTestOutput - Semi-manual asserts for .NET unit tests
Fluent Assertions - A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style unit tests. Targets .NET Framework 4.7, as well as .NET Core 2.1, .NET Core 3.0, .NET 6, .NET Standard 2.0 and 2.1. Supports the unit test frameworks MSTest2, NUnit3, XUnit2, MSpec, and NSpec3.