Time for another poll! We'd like to know which version of Visual Studio you're using with xUnit.net. dotnet.social/@xunit/11635...

Poll results: "Yes, we still use MTP v1" 0% "No, we only use MTP v2" 52% "No, we don't use MTP" 31% "I'm not sure what we use" 17%

We will be removing Microsoft Testing Platform v1 support from the next major release, moving to v2 as the default. We will still support your ability to choose to disable MTP as well. #DotNet #UnitTest

Just FYI: We're currently not planning any more releases on the main branch (3.x.y versions). We will be focused entirely on stabilizing and releasing 4.0.0.

There is an outstanding issue with Rider with v2, and I've let them know our plan to abandon v1. You can make tests work with v2 through some workarounds, but I'm not sure why this 6+ month old bug hasn't been prioritized yet, as v2 was released in October 2025 youtrack.jetbrains.com/issue/RIDER-...

NCrunch does not use a third party API. They use our first party API.

Sorry, this should've read "deprecating MTP v1".

We just shipped Core Framework v3 4.0.0-pre.33, Analyzers 2.0.0-pre.9, and VS Adapter 4.0.0-pre.3.

This prerelease build adds support for Native AOT, in addition to bug fixes.

xunit.net/releases/v3/...
xunit.net/releases/ana...
xunit.net/releases/vis...

#DotNet #CSharp #FSharp #UnitTest #TDD

There is a poll up on your Mastodon account about deprecating MTP v2 in the upcoming 4.0 release. Since there is no poll feature on Bluesky, we'll just link to the Mastodon post and you can vote there. dotnet.social/@xunit/11629...

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

Brad Wilson (@bradwilson@mastodon.social) Attached: 1 image Success! 🎉 The execution-side of @xunit@dotnet.social has been made native AOT compatible, resulting in our ability publish a native multi-assembly runner. Right now it's only able...

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

GitHub - Youssef1313/YTest.MTP.XUnit2 Contribute to Youssef1313/YTest.MTP.XUnit2 development by creating an account on GitHub.

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...?

.NET Runtime Identifier (RID) catalog - .NET Learn about the runtime identifier (RID) and how RIDs are used in .NET.

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

mastodon.social/@bradwilson/...

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).