Skip to main content

Migrating from XUnit v2 to v3 - What’s new?

The XUnit team decided to do a major overhaul of the XUnit libraries and created completely new V3 packages. So don't expect backwards compatibility but a significant architectural shift that brings improved performance, better isolation, and modernized APIs to .NET testing. While the migration requires some work, the benefits should make it worthwhile for most projects.

In this post I'll explain some of the reasons why I think you should consider migrating to the v3 version.

From libraries to executables

The most significant change in v3 is that test projects are now stand-alone executables rather than libraries that require external runners. This architectural shift solves several problems that plagued v2:

  • Dependency Resolution: The compiler now handles dependency resolution at build time instead of runtime
  • Process Isolation: Tests run in separate processes, providing better isolation than the Application Domain approach used in v2
  • Simplified Execution: You can directly run your test assembly without requiring separate runner tools

When you build a v3 test project, you get:

  • For .NET Framework: A .exe file that directly runs your tests
  • For .NET: A .dll file containing your tests plus a .exe stub launcher

This also aligns with the Microsoft.Test.Platform vision and decouples you from the Microsoft.NET.Test.Sdk.

If you still want to use the VSTest Runner, you can by referencing the Microsoft.NET.Test.Sdk project SDK and include the xunit.runner.visualstudio package.

Console, Trace and Debug output support

Starting from xUnit V3 output from Console, Trace and Debug statements can be captured. I think this is an improvement that will greatly help during debugging a failing test.

This feature is disabled by default for backwards compatibility but can be enabled easily by adding the following assembly-level attributes:

Share a single fixture among all the test classes

A feature that I missed compared to other testing frameworks was the lack of support for creating a single test context that could be used for all the tests in a test assembly. XUnit V3 solves this with the introduction of an Assembly Fixture. XUnit will create a single instance of this fixture and share it among all your test classes.

An example from the documentation:

More information

What's New in v3? [2025 August 14] | xUnit.net

Microsoft.Testing.Platform overview - .NET | Microsoft Learn

Microsoft Testing Platform [2025 June 7] | xUnit.net

Sharing Context between Tests | xUnit.net

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more