Skip to main content

Migrating from XUnit v2 to v3 – Getting started

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.

Yesterday I talked about some of the features that I like in the new version. Today I want to walk you through the basic steps needed to migrate an existing V2 project to V3.

Understanding the architectural changes

Before diving into the migration steps, it's crucial to understand the fundamental changes in xUnit v3 that impact how you'll structure and run your tests

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

Updated runtime requirements

xUnit v3 has modernized its minimum runtime requirements:

  • .NET Framework 4.7.2 or later
  • .NET 8 or later
  • Mono support is now officially supported on Linux and macOS

The framework targets .NET Standard 2.0, .NET Framework 4.7.2, and .NET 8, ensuring broad compatibility while dropping support for older runtimes.

SDK-style projects only

v3 only supports SDK-style projects. If you're still using older project formats, you'll need to migrate to SDK-style projects as part of this process.

Step-by-Step migration process

Step 1: Update NuGet Package References

The first step is updating your package references. Most packages have been renamed with a xunit.v3 prefix:

For a complete package migration table, check out the migration documentation: Migrating Unit Tests from v2 to v3

Remark: The xunit.abstractions package is no longer needed and should be removed entirely.

Step 2: Convert to Executable Project

Update your test project file to generate an executable instead of a library:

Step 3: Restore and Build

At this point, you should be able to restore packages:

dotnet restore
dotnet build

If the build succeeds, you can run your tests directly:

# Run the executable directly
./bin/Debug/net9.0/YourTestProject.exe

# Or use dotnet run
dotnet run

# With command line options
dotnet run -- -xml results.xml

Best Practices for v3

Use ValueTask for Async Tests

For better performance, prefer ValueTask over Task in async test methods:

Leverage improved Assertions

v3 includes new assertion methods and overloads. Review the what's new documentation to take advantage of these improvements.

Optimize test organization

With the new executable model, consider how you organize your test projects. You might benefit from splitting large test suites into multiple executable projects for better parallelization.

More information

Migrating Unit Tests from v2 to v3 [2025 April 12] | 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