should vs NFluent

should

Should Assertion Library (by erichexter)

Docs

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/) (by tpierrain)

Testing

Source Code

Docs

Suggest alternative

Edit details

Our great sponsors

WorkOS - The modern identity platform for B2B SaaS

InfluxDB - Power Real-Time Data Analytics at Scale

SaaSHub - Software Alternatives and Reviews

Our great sponsors

should		NFluent
	Project
1	Mentions	-
143	Stars	308
-	Growth	-
0.0	Activity	5.6
almost 5 years ago	Latest Commit	about 1 month ago
C#	Language	C#
GNU General Public License v3.0 or later	License	Apache License 2.0

The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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

Posts with mentions or reviews of should. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-03-01.

NUnit vs XUnit for .net6+ microservices
7 projects | /r/dotnet | 1 Mar 2023

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

NFluent

Posts with mentions or reviews of NFluent. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning NFluent yet.
Tracking mentions began in Dec 2020.

What are some alternatives?

When comparing should and NFluent you can also consider the following projects:

Shouldly - Should testing for .NET—the way assertions should be!

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.

GennyMcGenFace

Expecto - A smooth testing lib for F#. APIs made for humans! Strong testing methodologies for everyone!

Stryker.NET - Mutation testing for .NET core and .NET framework!

xUnit - xUnit.net is a free, open source, community-focused unit testing tool for .NET.

Machine.Specifications - Machine.Specifications is a Context/Specification framework for .NET that removes language noise and simplifies tests.

NUnit - NUnit Framework

NSubstitute - A friendly substitute for .NET mocking libraries.

Moq - Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]