xUnit.net
@xunit.net
xUnit.net is a free, open source, community-focused unit testing tool for .NET. Source is available at https://github.com/xunit/.
Currently maintained by https://mastodon.social/@bradwilson.
Currently maintained by https://mastodon.social/@bradwilson.
We marked the v2 packages as deprecated in NuGet as they will only be updated if we find security issues or catastrophic bugs, and to let people know that all new work is happening in the v3 packages.
Has this caused any undue grief to your teams? Chime in here: github.com/xunit/xunit/...
Has this caused any undue grief to your teams? Chime in here: github.com/xunit/xunit/...
Reconsider NuGet deprecation flag for xUnit.net v2 · Issue #3486 · xunit/xunit
Hi xUnit maintainers, I'm raising this to ask whether you'd consider removing the NuGet deprecated flag from the xunit v2 package (or, if removal isn't feasible, revising the NuGet deprecation mess...
github.com
February 8, 2026 at 5:50 PM
We marked the v2 packages as deprecated in NuGet as they will only be updated if we find security issues or catastrophic bugs, and to let people know that all new work is happening in the v3 packages.
Has this caused any undue grief to your teams? Chime in here: github.com/xunit/xunit/...
Has this caused any undue grief to your teams? Chime in here: github.com/xunit/xunit/...
The prerelease packages lists shown on our homepage are currently showing the latest release version instead. We have an open issue with shields.io to hopefully get that resolved: github.com/badges/shiel...
Clicking through will still show you the latest prerelease package (a login is required).
Clicking through will still show you the latest prerelease package (a login is required).
Shields.io
Concise, consistent, and legible badges
shields.io
January 17, 2026 at 5:14 PM
The prerelease packages lists shown on our homepage are currently showing the latest release version instead. We have an open issue with shields.io to hopefully get that resolved: github.com/badges/shiel...
Clicking through will still show you the latest prerelease package (a login is required).
Clicking through will still show you the latest prerelease package (a login is required).
We just shipped Core Framework v3 3.2.2 and Analyzers 1.27.0.
This includes new templates which default to Microsoft Testing Platform v2 and a new Native AOT compatible assertions package (plus bug fixes).
xunit.net/releases/v3/...
xunit.net/releases/ana...
#DotNet #CSharp #FSharp #UnitTest #TDD
This includes new templates which default to Microsoft Testing Platform v2 and a new Native AOT compatible assertions package (plus bug fixes).
xunit.net/releases/v3/...
xunit.net/releases/ana...
#DotNet #CSharp #FSharp #UnitTest #TDD
January 14, 2026 at 10:37 PM
We just shipped Core Framework v3 3.2.2 and Analyzers 1.27.0.
This includes new templates which default to Microsoft Testing Platform v2 and a new Native AOT compatible assertions package (plus bug fixes).
xunit.net/releases/v3/...
xunit.net/releases/ana...
#DotNet #CSharp #FSharp #UnitTest #TDD
This includes new templates which default to Microsoft Testing Platform v2 and a new Native AOT compatible assertions package (plus bug fixes).
xunit.net/releases/v3/...
xunit.net/releases/ana...
#DotNet #CSharp #FSharp #UnitTest #TDD
An update on getting native AOT console runners (to help compensate for deprecating Mono on non-Windows OSes) mastodon.social/@bradwilson/...
Brad Wilson (@[email protected])
Attached: 1 image
Success! 🎉 The execution-side of @[email protected] has been made native AOT compatible, resulting in our ability publish a native multi-assembly runner.
Right now it's only able...
mastodon.social
January 10, 2026 at 11:14 PM
An update on getting native AOT console runners (to help compensate for deprecating Mono on non-Windows OSes) mastodon.social/@bradwilson/...
Part of the work being done to move reports off XSL-T will include upgrading the NUnit XML report from v2 to v3 format. This will ship as part of 4.0.
January 5, 2026 at 9:33 AM
Part of the work being done to move reports off XSL-T will include upgrading the NUnit XML report from v2 to v3 format. This will ship as part of 4.0.
When we release 4.0, we will be switching the default Microsoft.Testing.Platform version from v1 to v2. This may cause compatibility issues with any dependent packages that are built for v1, hence waiting for a major version shift.
We will continue to support your option to choose v1.
We will continue to support your option to choose v1.
January 2, 2026 at 5:03 PM
When we release 4.0, we will be switching the default Microsoft.Testing.Platform version from v1 to v2. This may cause compatibility issues with any dependent packages that are built for v1, hence waiting for a major version shift.
We will continue to support your option to choose v1.
We will continue to support your option to choose v1.
The new options, shown here in Visual Studio 2026 and `dotnet new xunit3 -?`
December 31, 2025 at 1:33 AM
The new options, shown here in Visual Studio 2026 and `dotnet new xunit3 -?`
We are updating the `xunit3` project template in the next release:
* Offering a switch to choose MTP version: v2 (default), v1, or off
* Will not include VSTest support (`xunit.runner.visualstudio`) unless MTP is off
This updates the defaults for new projects without breaking back compat.
* Offering a switch to choose MTP version: v2 (default), v1, or off
* Will not include VSTest support (`xunit.runner.visualstudio`) unless MTP is off
This updates the defaults for new projects without breaking back compat.
December 30, 2025 at 11:30 PM
We are updating the `xunit3` project template in the next release:
* Offering a switch to choose MTP version: v2 (default), v1, or off
* Will not include VSTest support (`xunit.runner.visualstudio`) unless MTP is off
This updates the defaults for new projects without breaking back compat.
* Offering a switch to choose MTP version: v2 (default), v1, or off
* Will not include VSTest support (`xunit.runner.visualstudio`) unless MTP is off
This updates the defaults for new projects without breaking back compat.
New doc page: Using Microsoft.Testing.Platform with xUnit.net v2. xunit.net/docs/getting... #DotNet #UnitTest
Microsoft Testing Platform (xUnit.net v2) | xUnit.net
xunit.net
December 30, 2025 at 7:54 PM
New doc page: Using Microsoft.Testing.Platform with xUnit.net v2. xunit.net/docs/getting... #DotNet #UnitTest
Youssef (of the Microsoft TestFx team) is working on a personal project to add support for Microsoft.Testing.Platform to v2 projects, for those are not yet able to migrate to v3. github.com/Youssef1313/... #DotNet #UnitTest
GitHub - Youssef1313/YTest.MTP.XUnit2
Contribute to Youssef1313/YTest.MTP.XUnit2 development by creating an account on GitHub.
github.com
December 25, 2025 at 6:34 PM
Youssef (of the Microsoft TestFx team) is working on a personal project to add support for Microsoft.Testing.Platform to v2 projects, for those are not yet able to migrate to v3. github.com/Youssef1313/... #DotNet #UnitTest
The motivation for this is the removal of official support for Mono. Right now the console runner only builds for .NET Framework (4.7.2/4.8/4.8.1, for AnyCPU/x86). Removing official Mono support means maybe we should ship .NET versions now, too...?
December 20, 2025 at 8:54 PM
The motivation for this is the removal of official support for Mono. Right now the console runner only builds for .NET Framework (4.7.2/4.8/4.8.1, for AnyCPU/x86). Removing official Mono support means maybe we should ship .NET versions now, too...?
Is there interest in us shipping ready-made binaries of xunit.v3.runner.console (via the xunit.v3.runner.console NuGet package) that target .NET instead of .NET Framework? Which runtime IDs would you need to be supported? learn.microsoft.com/en-us/dotnet... #DotNet #UnitTest
.NET Runtime Identifier (RID) catalog - .NET
Learn about the runtime identifier (RID) and how RIDs are used in .NET.
learn.microsoft.com
December 20, 2025 at 8:52 PM
Is there interest in us shipping ready-made binaries of xunit.v3.runner.console (via the xunit.v3.runner.console NuGet package) that target .NET instead of .NET Framework? Which runtime IDs would you need to be supported? learn.microsoft.com/en-us/dotnet... #DotNet #UnitTest
Note: This is just the start of Native AOT support. This does not mean xUnit.net supports Native AOT yet; a lot more work has to go into the core framework before that will be the case.
December 11, 2025 at 2:36 AM
Note: This is just the start of Native AOT support. This does not mean xUnit.net supports Native AOT yet; a lot more work has to go into the core framework before that will be the case.
We're merging in the changes for a Native AOT compatible assertion library, because these files are frequently touched. The separation process makes them hard to merge over time.
Attached are lists of files added/changed in xunit/xunit and xunit/assert.xunit.
Attached are lists of files added/changed in xunit/xunit and xunit/assert.xunit.
December 11, 2025 at 2:36 AM
We're merging in the changes for a Native AOT compatible assertion library, because these files are frequently touched. The separation process makes them hard to merge over time.
Attached are lists of files added/changed in xunit/xunit and xunit/assert.xunit.
Attached are lists of files added/changed in xunit/xunit and xunit/assert.xunit.
The closest is indirect support from Microsoft via .NET Foundation, which includes ongoing sponsorship of our Visual Studio Enterprise license, as well as maintaining our CLAs and signing certificate.
December 8, 2025 at 7:11 PM
The closest is indirect support from Microsoft via .NET Foundation, which includes ongoing sponsorship of our Visual Studio Enterprise license, as well as maintaining our CLAs and signing certificate.
Ironically, we got supported for a while by Amazon via ".NET on AWS" but never Microsoft. 😂
December 8, 2025 at 7:10 PM
Ironically, we got supported for a while by Amazon via ".NET on AWS" but never Microsoft. 😂
We just celebrated our 40th GitHub Sponsor! Many thanks to the community for keeping the caffeine flowing for @bradwilson.dev 😄
December 8, 2025 at 6:13 PM
We just celebrated our 40th GitHub Sponsor! Many thanks to the community for keeping the caffeine flowing for @bradwilson.dev 😄
We just shipped Core Framework v3 3.2.1 and Analyzers 1.26.0.
This is primarily a bug fix release. Check the release notes for more information.
xunit.net/releases/v3/...
xunit.net/releases/ana...
#DotNet #CSharp #FSharp #UnitTest #TDD
This is primarily a bug fix release. Check the release notes for more information.
xunit.net/releases/v3/...
xunit.net/releases/ana...
#DotNet #CSharp #FSharp #UnitTest #TDD
Core Framework v3 3.2.1 | xUnit.net
xunit.net
November 28, 2025 at 10:49 PM
We just shipped Core Framework v3 3.2.1 and Analyzers 1.26.0.
This is primarily a bug fix release. Check the release notes for more information.
xunit.net/releases/v3/...
xunit.net/releases/ana...
#DotNet #CSharp #FSharp #UnitTest #TDD
This is primarily a bug fix release. Check the release notes for more information.
xunit.net/releases/v3/...
xunit.net/releases/ana...
#DotNet #CSharp #FSharp #UnitTest #TDD
We're going to start pushing CI builds for 4.0.0, as we have two feature branches that require a major version bump already. There's no planned release date yet (not even a planned NuGet release yet), so no idea how long the branch will live.
#DotNet #CSharp #FSharp #UnitTest #TDD
#DotNet #CSharp #FSharp #UnitTest #TDD
November 16, 2025 at 6:01 PM
We are updating the xUnit.net projects today to use .NET 10 SDK. If you want to pull the source and build, you will need the new SDK installed. dotnet.microsoft.com/download
We will be updating the documentation shortly for changes to Microsoft Testing Platform when using .NET 10 SDK.
We will be updating the documentation shortly for changes to Microsoft Testing Platform when using .NET 10 SDK.
Download .NET (Linux, macOS, and Windows) | .NET
Free downloads for building and running .NET apps on Linux, macOS, and Windows. Runtimes, SDKs, and developer packs for .NET Framework, .NET, and ASP.NET.
dotnet.microsoft.com
November 13, 2025 at 9:47 PM
We are updating the xUnit.net projects today to use .NET 10 SDK. If you want to pull the source and build, you will need the new SDK installed. dotnet.microsoft.com/download
We will be updating the documentation shortly for changes to Microsoft Testing Platform when using .NET 10 SDK.
We will be updating the documentation shortly for changes to Microsoft Testing Platform when using .NET 10 SDK.
If it's based on VSTest, you can still use it.
November 11, 2025 at 6:26 AM
If it's based on VSTest, you can still use it.