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/...
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).
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
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.
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.
The Visual Studio 2026 "New Project" UI, showing the two new options: "Test runner for 'dotnet test' and Test Explorer", and "Command line experience for 'dotnet run'".
Shows the new command line switches for "dotnet new xunit3": * "--test-runner" controls the test runner for "dotnet test" and Test Explorer, and has options for "mtp-v2", "mtp-v1", and "vstest". The default is "mtp-v2". * "--command-line" controls the command line experience for "dotnet run", and has options "xunit" and "mtp". The default is "xunit", and is only available when "--test-runner" is not set to "vstest".
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.
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
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
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.
A list of files changed in xunit/xunit. You can see the list in commit hash ba0a606d73ece9dbb2755bb8d41b4a9f37dda70c.
A list of files changed in xunit/assert.xunit. You can see the list in commit hash f8375ef34d2f0584009c78f3bb11b1a57dd8b12f.
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.
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. 😂
We just celebrated our 40th GitHub Sponsor! Many thanks to the community for keeping the caffeine flowing for @bradwilson.dev 😄
We are considering dropping support for Mono from the next major version. (It will likely continue to work, we just won't officially support it.)
Are you still using Mono to run tests? If so, on which OSes? #DotNet #UnitTest
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
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
Note that this only affects building xUnit.net itself. The minimum target frameworks for using xUnit.net remain unchanged (net472 and net8.0).
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.
Yep
If it's based on VSTest, you can still use it.
If you are using a test case orderer today (implementing `ITestCaseOrderer`), take a peek at this issue that wants to introduce `ITestClassOrderer` and `ITestMethodOrderer` and the impact it has on developers using test case orderers today. Feedback welcome! github.com/xunit/xunit/...
We just shipped Core Framework v3 3.2.0 and Analyzers 1.25.0.
This includes optional support for Microsoft Testing Platform v2. Check the release notes for more information.
xunit.net/releases/v3/...
xunit.net/releases/ana...
#DotNet #CSharp #FSharp #UnitTest #TDD
Microsoft.Testing.Platform v2 support is now available in a prerelease CI build. Note that we will continue to support v1 by default; you must opt into v2.
More information: github.com/xunit/xunit/...
#DotNet #MicrosoftTestingPlatform
Just a reminder that we have delayed plans to support MTP v2. Any attempt to use any parts of MTP v2 with xUnit.net v3 will result in failure due to incompatibilities.
Not really. The fundamental collision appears to be in the fact that we always support MTP vs other frameworks that "mix in" support at build time, combined with changes coming to how `dotnet test` works in .NET 10, plus restrictions put into the design of MTP v2.
Too much for a medium like this.
