Testing on Dimitri Laaraybi

Exploring TUnit, a modern take on .NET testing

Tue, 27 Jan 2026 00:00:00 +0000

The .NET testing ecosystem has been dominated for years by well‑established frameworks such as xUnit, NUnit, and MSTest. They are mature, stable, and battle‑tested. But as .NET itself evolves, becoming faster, more async‑friendly, and more careful about performance, new tools are emerging to better match these modern expectations.

One of the most interesting newcomers is TUnit .

In this article, we’ll try to explore what TUnit is, its core concepts and advantages, but also explore concrete examples of tests compared to xUnit.
Let’s go ! 🔥

No, FluentAssertions is not the only one... Here is how to switch from FluentAssertions to Shouldly !

Sun, 02 Mar 2025 00:00:00 +0000

Introduction

Hey all ! 🫡

Let’s talk about another little drama that has been shaking the .NET community during the last weeks.
When working on unit tests in .NET, developers often rely on assertion libraries to make their tests more readable and expressive.
Two popular libraries in this space are FluentAssertions and Shouldly. While both libraries serve the same purpose, one of them actually updated its licensing model and frightened the whole community about his new goal, making money 😂 (Well who does not want to)
And this one is FluentAssertions.
In fact, it now requires a paid licence to be used for commercial use. At least, concerning the 8.x.x version. The developers have stated that the 7.x.x version will be forever free and receive critical fixes, but this strange move from their side may have pushed you to find another library for your assertions, to avoid any problems with the company you work for.
If that’s the case, here is a little tutorial that explains how to migrate from FluentAssertions to Shouldly !

How to switch from Moq to NSubstitute after the SponsorLink scandal ?

Thu, 17 Aug 2023 00:00:00 +0000

Hey devs ! 😁

If you are a .NET developer who uses the popular mocking library Moq for your unit tests, you may have heard about the recent controversy that erupted when it was revealed that Moq was secretly collecting and sending user email addresses to a third-party service called SponsorLink. This was done without the consent or knowledge of the developers who used Moq , and raised serious privacy and security concerns.
In this post, I’ll try to explain in more details what this scandal is all about and how to switch from Moq to NSubstitute if you see fit, but also how to prevent your projects from those vulnerabilities in a DevSecOps way 😉