Heard about the recent Fluent Assertions disaster … that’s unfortunate. We barely got to use the otherwise super nice library. And now with their change in licensing strategy we will with a very high chance switch to something else.
Shouldly looks nice 👍🏻
Shouldly looks nice 👍🏻
January 16, 2025 at 5:09 PM
Heard about the recent Fluent Assertions disaster … that’s unfortunate. We barely got to use the otherwise super nice library. And now with their change in licensing strategy we will with a very high chance switch to something else.
Shouldly looks nice 👍🏻
Shouldly looks nice 👍🏻
Maybe time to switch to Shouldly 🤔 github.com/shouldly/sho... #dotnet
GitHub - shouldly/shouldly: Should testing for .NET—the way assertions should be!
Should testing for .NET—the way assertions should be! - shouldly/shouldly
github.com
January 15, 2025 at 8:48 AM
Maybe time to switch to Shouldly 🤔 github.com/shouldly/sho... #dotnet
From the archives...
Testing in .NET with xUnit + NSubstitute + Shouldly
https://barretblake.dev/posts/development/2026/04/testing-dotnet/ #testing #dotnet #xunit #nsubstitute #shouldly
Testing in .NET with xUnit + NSubstitute + Shouldly
https://barretblake.dev/posts/development/2026/04/testing-dotnet/ #testing #dotnet #xunit #nsubstitute #shouldly
May 19, 2026 at 7:00 PM
From the archives...
Testing in .NET with xUnit + NSubstitute + Shouldly
https://barretblake.dev/posts/development/2026/04/testing-dotnet/ #testing #dotnet #xunit #nsubstitute #shouldly
Testing in .NET with xUnit + NSubstitute + Shouldly
https://barretblake.dev/posts/development/2026/04/testing-dotnet/ #testing #dotnet #xunit #nsubstitute #shouldly
New post from my blog...
In case you missed it earlier...
Testing in .NET with xUnit + NSubstitute + Shouldly
https://barretblake.dev/posts/development/2026/04/testing-dotnet/ #testing #dotnet #xunit #nsubstitute #shouldly
In case you missed it earlier...
Testing in .NET with xUnit + NSubstitute + Shouldly
https://barretblake.dev/posts/development/2026/04/testing-dotnet/ #testing #dotnet #xunit #nsubstitute #shouldly
April 29, 2026 at 9:30 PM
New post from my blog...
In case you missed it earlier...
Testing in .NET with xUnit + NSubstitute + Shouldly
https://barretblake.dev/posts/development/2026/04/testing-dotnet/ #testing #dotnet #xunit #nsubstitute #shouldly
In case you missed it earlier...
Testing in .NET with xUnit + NSubstitute + Shouldly
https://barretblake.dev/posts/development/2026/04/testing-dotnet/ #testing #dotnet #xunit #nsubstitute #shouldly
New post from my blog...
Testing in .NET with xUnit + NSubstitute + Shouldly
https://barretblake.dev/posts/development/2026/04/testing-dotnet/ #testing #dotnet #xunit #nsubstitute #shouldly
Testing in .NET with xUnit + NSubstitute + Shouldly
https://barretblake.dev/posts/development/2026/04/testing-dotnet/ #testing #dotnet #xunit #nsubstitute #shouldly
April 29, 2026 at 1:15 PM
New post from my blog...
Testing in .NET with xUnit + NSubstitute + Shouldly
https://barretblake.dev/posts/development/2026/04/testing-dotnet/ #testing #dotnet #xunit #nsubstitute #shouldly
Testing in .NET with xUnit + NSubstitute + Shouldly
https://barretblake.dev/posts/development/2026/04/testing-dotnet/ #testing #dotnet #xunit #nsubstitute #shouldly
If your looking for a fluent assertions alternative in the dotnet space then take a look at Shouldly:
github.com/shouldly/sho...
github.com/shouldly/sho...
GitHub - shouldly/shouldly: Should testing for .NET—the way assertions should be!
Should testing for .NET—the way assertions should be! - shouldly/shouldly
github.com
January 17, 2025 at 11:25 AM
If your looking for a fluent assertions alternative in the dotnet space then take a look at Shouldly:
github.com/shouldly/sho...
github.com/shouldly/sho...
docs.shouldly.org/documentatio... - Shouldly doesn't have AssertionScope, but SatisfyAllConditions() is close.
SatisfyAllConditions | Shouldly
snippet source | anchor
docs.shouldly.org
August 21, 2025 at 3:03 PM
docs.shouldly.org/documentatio... - Shouldly doesn't have AssertionScope, but SatisfyAllConditions() is close.
github.com/kmtchl/Fluen... - Convert from #FluentAssertions to #Shouldly. Nice work github.com/kmtchl.
GitHub - kmtchl/FluentAssertionsToShoudlyConverter
Contribute to kmtchl/FluentAssertionsToShoudlyConverter development by creating an account on GitHub.
github.com
February 28, 2025 at 4:55 PM
github.com/kmtchl/Fluen... - Convert from #FluentAssertions to #Shouldly. Nice work github.com/kmtchl.
https://github.com/shouldly/shouldly/issues/1034 - a migration guide from FluentAssertions to Shouldly. Excellent work https://github.com/felipextrindade #dotNET #testing
Onboarding guide for FluentAssertions · Issue #1034 · shouldly/shouldly
Hi 🙋♂️. I'm Nico Jansen, a manager at Info Support. For years, we've sponsored FluentAssertions, a comparable assertion library. My colleagues also contributed a lot of code to the project.…
github.com
February 18, 2025 at 4:29 PM
https://github.com/shouldly/shouldly/issues/1034 - a migration guide from FluentAssertions to Shouldly. Excellent work https://github.com/felipextrindade #dotNET #testing
docs.shouldly.org - Shouldly is a great replacement for FluentAssertions. It isn't quite a drop-in replacement, but it's close. For the most part, replace `.Should().Be(` with `.ShouldBe(`. #dotNET #testing
Overview | Shouldly
docs.shouldly.org
February 17, 2025 at 11:09 PM
docs.shouldly.org - Shouldly is a great replacement for FluentAssertions. It isn't quite a drop-in replacement, but it's close. For the most part, replace `.Should().Be(` with `.ShouldBe(`. #dotNET #testing
My favorite unit testing related libraries at the moment are Shouldly (http://shouldly.github.com/) and NSubstitute (http://nsubstitute.github.com/).
November 16, 2024 at 1:29 AM
My favorite unit testing related libraries at the moment are Shouldly (http://shouldly.github.com/) and NSubstitute (http://nsubstitute.github.com/).
This was long before ChatGPT existed and offered a suggestions in the IDE to convert it to Shouldly assertion, but ChatGPT could probably do the job these days :D
January 16, 2025 at 9:29 AM
This was long before ChatGPT existed and offered a suggestions in the IDE to convert it to Shouldly assertion, but ChatGPT could probably do the job these days :D
👀 Looking for a clean way to write assertions in your #csharp tests? Consider Shouldly!
📝 In this post, Scott talks us through how to work with Shouldly using .NET 9 and XUnit:
https://blog.nimblepros.com/blogs/getting-started-with-shouldly/
#dotnet #testing
📝 In this post, Scott talks us through how to work with Shouldly using .NET 9 and XUnit:
https://blog.nimblepros.com/blogs/getting-started-with-shouldly/
#dotnet #testing
January 20, 2025 at 7:00 PM
👀 Looking for a clean way to write assertions in your #csharp tests? Consider Shouldly!
📝 In this post, Scott talks us through how to work with Shouldly using .NET 9 and XUnit:
https://blog.nimblepros.com/blogs/getting-started-with-shouldly/
#dotnet #testing
📝 In this post, Scott talks us through how to work with Shouldly using .NET 9 and XUnit:
https://blog.nimblepros.com/blogs/getting-started-with-shouldly/
#dotnet #testing
January 14, 2025 at 5:23 PM
I'd pay $100US if they (Xceed) can -honestly- release their purchase order numbers.
Have 10 people purchased it yet? in 6 months time?
Maybe we're all the f00ls?
Also related: github.com/shouldly/sho...
Have 10 people purchased it yet? in 6 months time?
Maybe we're all the f00ls?
Also related: github.com/shouldly/sho...
⭐🚀Welcome ex-FluentAssertion consumers 🤘🏻 · Issue #1033 · shouldly/shouldly
Welcome to Shouldy! You'll love it here! (please mods, lets keep this fun open for a few days at least....)
github.com
January 16, 2025 at 12:22 PM
I'd pay $100US if they (Xceed) can -honestly- release their purchase order numbers.
Have 10 people purchased it yet? in 6 months time?
Maybe we're all the f00ls?
Also related: github.com/shouldly/sho...
Have 10 people purchased it yet? in 6 months time?
Maybe we're all the f00ls?
Also related: github.com/shouldly/sho...
In this case I'm using it to replace uses of FluentAssertions with Shouldly. But it only updates half of them. Then I have to tell it it missed some and should replace them all. After that all are correctly replaced. I have no idea why it doesn't just do it in one attempt.
February 12, 2025 at 12:22 PM
In this case I'm using it to replace uses of FluentAssertions with Shouldly. But it only updates half of them. Then I have to tell it it missed some and should replace them all. After that all are correctly replaced. I have no idea why it doesn't just do it in one attempt.
🚀 Neat! #duende is sponsoring #dotnet project Shouldy for the next year for $3,000. #unittesting #xunit #nunit #mstest
https://blog.duendesoftware.com/posts/20250415-shouldly-assertion-framework/
https://blog.duendesoftware.com/posts/20250415-shouldly-assertion-framework/
Duende Software Blog
We help companies using .NET to build identity and access control solutions for modern applications.
blog.duendesoftware.com
April 15, 2025 at 12:55 PM
🚀 Neat! #duende is sponsoring #dotnet project Shouldy for the next year for $3,000. #unittesting #xunit #nunit #mstest
https://blog.duendesoftware.com/posts/20250415-shouldly-assertion-framework/
https://blog.duendesoftware.com/posts/20250415-shouldly-assertion-framework/
What did you decide to go with? Shouldly or NUnit/xUnit assertions or other options?
January 15, 2025 at 3:41 PM
What did you decide to go with? Shouldly or NUnit/xUnit assertions or other options?
Probably quicker to move to AwesomeAsertions or Shouldly
January 17, 2025 at 12:21 PM
Probably quicker to move to AwesomeAsertions or Shouldly
Done it for a couple of our projects. Mostly you can do replace `Should().` with `Should`, ex: FA:s Should().BeTrue() can be replaced ShouldBeTrue() in Shouldly. There are some methods no available in Shouldly though, like stream.Should().BeReadable().
January 30, 2025 at 2:27 PM
Done it for a couple of our projects. Mostly you can do replace `Should().` with `Should`, ex: FA:s Should().BeTrue() can be replaced ShouldBeTrue() in Shouldly. There are some methods no available in Shouldly though, like stream.Should().BeReadable().
I think for an assertion library it's quite expensive, especially when it's a cost per developer and year! We are moving to Shouldly instead: easy enough conversion.
January 17, 2025 at 1:57 PM
I think for an assertion library it's quite expensive, especially when it's a cost per developer and year! We are moving to Shouldly instead: easy enough conversion.
I just open-sourced my test assertion library for Swift, which I've been using in one of my projects for a while.
The new test framework in Swift 6 is a significant improvement, but I was missing Shouldly from .NET too much.
github.com/patriksvenss...
The new test framework in Swift 6 is a significant improvement, but I was missing Shouldly from .NET too much.
github.com/patriksvenss...
October 20, 2024 at 10:49 AM
I just open-sourced my test assertion library for Swift, which I've been using in one of my projects for a while.
The new test framework in Swift 6 is a significant improvement, but I was missing Shouldly from .NET too much.
github.com/patriksvenss...
The new test framework in Swift 6 is a significant improvement, but I was missing Shouldly from .NET too much.
github.com/patriksvenss...
January 15, 2025 at 6:58 AM