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