should
NSubstitute
Our great sponsors
should | NSubstitute | |
---|---|---|
1 | 11 | |
143 | 2,550 | |
- | 1.5% | |
0.0 | 7.4 | |
almost 5 years ago | 2 days 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.
should
-
NUnit vs XUnit for .net6+ microservices
On a side note, something I would highly recommend NOT doing is using the built in assertion types for any of the test adapters. Without a doubt the hardest part of switching unit test frameworks is having to fix all your assertions which is why we use 3rd party assertions. The built-in assertions also tend to not be very feature rich and don't have the most helpful messages. We personally use FluentAssertions, but there are other options such as Shoudly or Should. I highly recommend picking one of them over the built in assertions. You will thank yourself later :)
NSubstitute
-
What am I missing about interfaces?
a. you might do so purely out of argo cult, i.e. because someone told you this was the right thing to do™, and that's a silly exercise. b. you could also be doing this for a good reason: to use the interface with a mocking tool like NSubstitute
-
The Moq-gate: You Either Die a Hero...
When comparing it to one of its most well-known alternatives, NSubstitute, which has "only" reached 85.6 million downloads, it is fair to say that Moq is the most widely used mocking library in the .NET ecosystem.
-
Since v4.20, Moq is harvesting email addresses
Maintainer rejected the PR. They have temporarily disabled the integration in https://github.com/moq/moq/pull/1375 but kept the SponsorLink project reference in the source code. It seems like their intent is to re-enable the integration at a later point :(
NSubstitute [0] might be an alternative. Or to fork Moq pre-4.20.
[0] https://nsubstitute.github.io/
-
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.
- [AskJS] Can we talk about Stubs, Spies and Mocks in JavaScript and what a mess they are?
-
Coincidence? I think not
it will change the URL from https://github.com/nsubstitute/NSubstitute to https://github.dev/nsubstitute/NSubstitute (or you can just nav there yourself).
-
I need a C# crash course for experienced developers
NSubstitute
-
Moq vs NSubstitute: syntax cheat sheet
🔗 NSubstitute documentation | NSubstitute
-
My Top N Favorite Plugins and Tools for Developers
If you use NSubstitute (the best mocking .NET framework), then you have to install this small yet useful plugin right now. It kindly generates mocks and Arg.Is / Arg.Any.
-
Dot net libraries/tools that are usefull in many projects
Another nice mocking framework is NSubstitute https://nsubstitute.github.io/
What are some alternatives?
Shouldly - Should testing for .NET—the way assertions should be!
Moq - Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]
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.
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.
GennyMcGenFace
FakeItEasy - The easy mocking library for .NET
NFluent - Smooth your .NET TDD experience with NFluent! NFluent is an ergonomic assertion library which aims to fluent your .NET TDD experience (based on simple Check.That() assertion statements). NFluent aims your tests to be fluent to write (with a super-duper-happy 'dot' auto-completion experience), fluent to read (i.e. as close as possible to plain English expression), but also fluent to troubleshoot, in a less-error-prone way comparing to the classical .NET test frameworks. NFluent is also directly inspired by the awesome Java FEST Fluent assertion/reflection library (http://fest.easytesting.org/)
NUnit - NUnit Framework
Stryker.NET - Mutation testing for .NET core and .NET framework!
Rhino Mocks
Machine.Specifications - Machine.Specifications is a Context/Specification framework for .NET that removes language noise and simplifies tests.
Bogus - :card_index: A simple fake data generator for C#, F#, and VB.NET. Based on and ported from the famed faker.js.