Code Quality Rank: L4
Programming language: C#
License: GNU General Public License v3.0 or later
Tags: Framework     Test     Unit     Testing     TDD     AAA     Should     Testunit     Rspec     Assert     Assertion    
Latest version: v4.0.1

Shouldly alternatives and similar packages

Based on the "Testing" category.
Alternatively, view Shouldly alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of Shouldly or a related project?

Add another 'Testing' Package


Shouldly Logo

CI NuGet NuGet Join the chat at https://gitter.im/shouldly/shouldly

Shouldly is an assertion framework which focuses on giving great error messages when the assertion fails while being simple and terse.

This is the old Assert way:

Assert.That(contestant.Points, Is.EqualTo(1337));

For your troubles, you get this message, when it fails:

Expected 1337 but was 0

How it Should be:


Which is just syntax, so far, but check out the message when it fails:

contestant.Points should be 1337 but was 0

It might be easy to underestimate how useful this is. Another example, side by side:

Assert.That(map.IndexOfValue("boo"), Is.EqualTo(2));    // -> Expected 2 but was -1
map.IndexOfValue("boo").ShouldBe(2);                    // -> map.IndexOfValue("boo") should be 2 but was -1

Shouldly uses the code before the ShouldBe statement to report on errors, which makes diagnosing easier.

Read more about Shouldly and its features at https://docs.shouldly.io/.


Shouldly can be found here on NuGet and can be installed by copying and pasting the following command into your Package Manager Console within Visual Studio (Tools > NuGet Package Manager > Package Manager Console).

Install-Package Shouldly

Alternatively if you're using .NET Core then you can install Shouldly via the command line interface with the following command:

dotnet add package Shouldly


Contributions to Shouldly are very welcome. For guidance, please see [CONTRIBUTING.md](CONTRIBUTING.md)

Pre-requisites for running on build server

Shouldly uses the source code to make its error messages better. Hence, on the build server you will need to have the "full" pdb files available where the tests are being run.

What is meant by "full" is that when you set up your "release" configuration in Visual Studio and you go to Project Properties > Build > Advanced > Debug, you should set it to "full" rather than "pdb-only".

Currently maintained by

If you are interested in helping out, jump on Gitter and have a chat.

Brought to you by

  • Dave Newman
  • Xerxes Battiwalla
  • Anthony Egerton
  • Peter van der Woude
  • Jake Ginnivan