Sign in

xUnit.net

@xunit.net
346 followers 1 following 148 posts

xUnit.net is a free, open source, community-focused unit testing tool for .NET. Source is available at github.com/xunit. Currently maintained by mastodon.social/@bradwilson.

PostsRepliesMedia
xUnit.net @xunit.net · 12/09/2026
We just shipped Core Framework v3 4.0.1 and Analyzers 2.1.0. This release includes a new Markdown report and several bug fixes. xunit.net/releases/v3/... xunit.net/releases/ana... #DotNet #CSharp #FSharp #UnitTest #TDD
xunit.net
Core Framework v3 4.0.1 | xUnit.net
021
xUnit.net @xunit.net · 11/09/2026
Are you still using .NET Framework with xUnit.net? If so, what's keeping you there, and when might you stop? (No polls on bsky or we would've done one, like we did on Mastodon.)
221
xUnit.net @xunit.net · 05/09/2026
We will be shipping Core Framework v3 4.0.1 and Analyzers 2.0.1 in about a week. If you haven't upgraded to 4.0.0 yet, now would be a good time to give it a try and report any issues you discover. Thanks!
021
xUnit.net @xunit.net · 17/08/2026
Unfortunately, unlike with our own CLI, MTP does not offer us a way to provide an unlisted switch that we can deprecate (and, more importantly, make that switch not collide). We already know an MTP-offered `-report-ctrf` is coming soon (if not already available).
000
xUnit.net @xunit.net · 17/08/2026
Sorry, we missed the updated command line switches for MTP in the release notes. They've been updated: xunit.net/releases/v3/...
xunit.net
Core Framework v3 4.0.0 | xUnit.net
200
xUnit.net @xunit.net · 15/08/2026
We just shipped Core Framework v3 4.0.0, Analyzers 2.0.0, and VS Adapter 4.0.0. This is a major release with many new features. Check the release notes for the details! xunit.net/releases/v3/... xunit.net/releases/ana... xunit.net/releases/vis... #DotNet #CSharp #FSharp #UnitTest #TDD
xunit.net
Core Framework v3 4.0.0 | xUnit.net
162
xUnit.net @xunit.net · 27/07/2026
Good news! Rider 2026.2 has resolved their issues with Microsoft Testing Platform v2 and xUnit.net v3. Check this issue comment for more information: youtrack.jetbrains.com/issue/RIDER-...
021
xUnit.net @xunit.net · 18/07/2026
We just shipped Core Framework v3 4.0.0-pre.154, Analyzers 2.0.0-pre.60, and VS Adapter 4.0.0-pre.5. This release adds support for full test parallelization and a new analyzer, in addition to bug fixes. xunit.net/releases/v3/... xunit.net/releases/ana... xunit.net/releases/vis...
xunit.net
Core Framework v3 4.0.0-pre.154 | xUnit.net
000
xUnit.net @xunit.net · 01/06/2026
Indeed. Thanks!
010
xUnit.net @xunit.net · 31/05/2026
We have posted our new code of conduct, which prohibits any contributions that are created in whole or part with AI or LLMs. This is not limited to code contributions. xunit.net/code-of-cond...
xunit.net
Code of Conduct | xUnit.net
130
xUnit.net @xunit.net · 31/05/2026
We just shipped Core Framework v3 4.0.0-pre.128 and Analyzers 2.0.0-pre.56. This release is primarily a bug fix release with a few small features. xunit.net/releases/v3/... xunit.net/releases/ana... #DotNet #CSharp #FSharp #UnitTest #TDD
xunit.net
Core Framework v3 4.0.0-pre.128 | xUnit.net
020
xUnit.net @xunit.net · 02/05/2026
We just shipped Core Framework v3 4.0.0-pre.108 and Analyzers 2.0.0-pre.51. This release adds new features, new analyzers, and fixed several bugs. We anticipate these being the final prerelease builds of this cycle. Please test thoroughly! xunit.net/releases/v3/... xunit.net/releases/ana...
xunit.net
Core Framework v3 4.0.0-pre.108 | xUnit.net
000
xUnit.net @xunit.net · 28/04/2026
There will be another prerelease coming this weekend. Since we like to have prerelease builds stable for a month before declaring them release, please make sure to use the current and upcoming builds to verify, especially with Native AOT. Thanks! #DotNet #UnitTest #NativeAOT #CSharp
011
xUnit.net @xunit.net · 12/04/2026
Based on this poll, we will be removing support for Visual Studio 2019 and out-of-support versions of Visual Studio 2022 from `xunit.analyzers` sometime before the final 2.0.0 release.
A poll about Visual Studio usage with xUnit.net.

0% voted for VS 2019
0% voted for VS 2022 (older than 17.8)
7% voted for VS 2022 (17.8 or newer)
93% voted for VS 2026
040
xUnit.net @xunit.net · 12/04/2026
We just shipped Core Framework v3 4.0.0-pre.81, Analyzers 2.0.0-pre.40, and VS Adapter 4.0.0-pre.4. This release adds several new analyzers and fixes many bugs, especially related to Native AOT support. xunit.net/releases/v3/... xunit.net/releases/ana... xunit.net/releases/vis... #DotNet #CSharp
xunit.net
Core Framework v3 4.0.0-pre.81 | xUnit.net
030
xUnit.net @xunit.net · 09/04/2026
Do you write custom TraitAttribute-derived attributes? Do you think they'd be useful in the core framework? If so, chime in with your suggestions here: github.com/xunit/xunit/... #DotNet #UnitTest #CSharp
github.com
Do you make custom TraitAttributes? · xunit xunit · Discussion #3537
With the introduction of Native AOT, we lose both access to ITraitAttribute and the ability to create your own custom trait attribute by deriving from TraitAttribute. This is further complicated by...
000
xUnit.net @xunit.net · 05/04/2026
Time for another poll! We'd like to know which version of Visual Studio you're using with xUnit.net. dotnet.social/@xunit/11635...
dotnet.social
xUnit.net (@xunit@dotnet.social)
What version of Visual Studio are you using with xUnit.net? [ ] VS 2019 [ ] VS 2022 (< 17.8) [ ] VS 2022 (>= 17.8) [ ] VS 2026
000
xUnit.net @xunit.net · 01/04/2026
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
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%
193
xUnit.net @xunit.net · 26/03/2026
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.
000
xUnit.net @xunit.net · 26/03/2026
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-...
youtrack.jetbrains.com
100
xUnit.net @xunit.net · 26/03/2026
NCrunch does not use a third party API. They use our first party API.
100
xUnit.net @xunit.net · 25/03/2026
Sorry, this should've read "deprecating MTP v1".
000
xUnit.net @xunit.net · 25/03/2026
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
xunit.net
Release Notes | xUnit.net
161
xUnit.net @xunit.net · 25/03/2026
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...
dotnet.social
xUnit.net (@xunit@dotnet.social)
We are considering removing support for Microsoft Testing Platform v1 from the upcoming 4.0 release. Would this be a problem for you? [ ] Yes, we still use MTP v1 [ ] No, we only use MTP v2 [ ] No, w...
213
xUnit.net @xunit.net · 08/02/2026
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/...
github.com
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...
031
xUnit.net @xunit.net · 17/01/2026
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).
shields.io
Shields.io
Concise, consistent, and legible badges
000
xUnit.net @xunit.net · 14/01/2026
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
070
xUnit.net @xunit.net · 10/01/2026
An update on getting native AOT console runners (to help compensate for deprecating Mono on non-Windows OSes) mastodon.social/@bradwilson/...
mastodon.social
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...
000
xUnit.net @xunit.net · 05/01/2026
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.
000
xUnit.net @xunit.net · 02/01/2026
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.
011
xUnit.net @xunit.net · 31/12/2025
The new options, shown here in Visual Studio 2026 and `dotnet new xunit3 -?`
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".
000
xUnit.net @xunit.net · 30/12/2025
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.
122
xUnit.net @xunit.net · 30/12/2025
New doc page: Using Microsoft.Testing.Platform with xUnit.net v2. xunit.net/docs/getting... #DotNet #UnitTest
xunit.net
Microsoft Testing Platform (xUnit.net v2) | xUnit.net
021
xUnit.net @xunit.net · 25/12/2025
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.com
GitHub - Youssef1313/YTest.MTP.XUnit2
Contribute to Youssef1313/YTest.MTP.XUnit2 development by creating an account on GitHub.
040
xUnit.net @xunit.net · 20/12/2025
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...?
000
xUnit.net @xunit.net · 20/12/2025
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
learn.microsoft.com
.NET Runtime Identifier (RID) catalog - .NET
Learn about the runtime identifier (RID) and how RIDs are used in .NET.
111
xUnit.net @xunit.net · 11/12/2025
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.
000
xUnit.net @xunit.net · 11/12/2025
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.
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.
120
xUnit.net @xunit.net · 08/12/2025
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.
120
xUnit.net @xunit.net · 08/12/2025
Ironically, we got supported for a while by Amazon via ".NET on AWS" but never Microsoft. 😂
140
xUnit.net @xunit.net · 08/12/2025
We just celebrated our 40th GitHub Sponsor! Many thanks to the community for keeping the caffeine flowing for @bradwilson.dev 😄
041
xUnit.net @xunit.net · 04/12/2025
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
000
xUnit.net @xunit.net · 28/11/2025
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
xunit.net
Core Framework v3 3.2.1 | xUnit.net
040
xUnit.net @xunit.net · 22/11/2025
mastodon.social/@bradwilson/...
mastodon.social
Brad Wilson (@bradwilson@mastodon.social)
Pondering what big breaking change feature(s) I could add for the 4.0 release of @xunit@dotnet.social. Many of these would qualify: https://github.com/xunit/xunit/issues?q=is%3Aissue%20is%3Aopen%20sor...
000
xUnit.net @xunit.net · 16/11/2025
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
050
xUnit.net @xunit.net · 13/11/2025
Note that this only affects building xUnit.net itself. The minimum target frameworks for using xUnit.net remain unchanged (net472 and net8.0).
000
xUnit.net @xunit.net · 13/11/2025
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.
dotnet.microsoft.com
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.
010
xUnit.net @xunit.net · 11/11/2025
Yep
100
xUnit.net @xunit.net · 11/11/2025
If it's based on VSTest, you can still use it.
100
xUnit.net @xunit.net · 10/11/2025
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/...
github.com
Can ITestClassOrderer be added to complete the ordering support on all levels? · Issue #3424 · xunit/xunit
✅ Assembly is a list of collections - we can order those with ITestCollectionOrderer ❌ Collection is a list of classes - we can not order those (request for ITestClassOrderer) ✅ Class is a list of ...
010