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.

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

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

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.

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.

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.

We just shipped Core Framework v3 3.1.0 and Visual Studio adapter 3.1.5. Check the release notes for new features and bugs fixed. xunit.net/releases/v3/... xunit.net/releases/vis... #DotNet #CSharp #FSharp #UnitTest #TDD

Thank you @bitwarden.bsky.social for your generous support of xUnit.net! github.com/sponsors/xunit

We just shipped Core Framework v3 3.2.0-pre.5. This is specifically for users who wish to try the preview of Microsoft Testing Platform v2. Estimated RTM for 3.2.0 will be close to .NET 10 RTM. 3.1.0 RTM will be later this month. xunit.net/releases/v3/... #DotNet #CSharp #FSharp #UnitTest #TDD

We just shipped Core Framework v3 3.0.1, Analyzers 1.24.0, and Visual Studio adapter 3.1.4. Check the release notes for new features and bugs fixed. xunit.net/releases/v3/... xunit.net/releases/ana... xunit.net/releases/vis... #DotNet #CSharp #FSharp #UnitTest #TDD

The last core framework release was July 13. We definitely have enough for a new release next week. If you're so inclined, maybe pick up a CI build and test it before we ship and/or raise awareness of anything you want fixed. xunit.net/docs/using-c... #DotNet #CSharp #FSharp #UnitTest #TDD

Given that xUnit.net runs tests in random order by default, would changing the randomization order (in order to fix a bug) just be considered a bug fix or a breaking change? Asking for a SemVer. (Poll is on Mastodon, as Bluesky doesn't have polls.) dotnet.social/@xunit/11493... #DotNet #UnitTest

Wrote a little bit about Microsoft Testing Platform and @xunit.net Read it here: blog.ostebaronen.dk/2025/07/ms-t... #dotnet #testing

We just shipped Visual Studio adapter 3.1.3. This is a bug fix release to address a failure case when running xUnit.net v2 tests. xunit.net/releases/vis... #DotNet #CSharp #FSharp #UnitTest #TDD

We just shipped Core Framework v3 3.0.0, Analyzers 1.23.0, and Visual Studio adapter 3.1.2. Check the release notes for breaking changes, new features, and bugs fixed. xunit.net/releases/v3/... xunit.net/releases/ana... xunit.net/releases/vis... #DotNet #CSharp #FSharp #UnitTest #TDD

In preparation for publishing v3 3.0.0, we've switched over to the new website at xunit.net (and new.xunit.net is no longer published). The new content lives at github.com/xunit/xunit.... (the old `gh-pages` branch of xunit/xunit will be deleted soon). Let us know of any issues with the new site!

We just shipped a new prerelease build of the core framework (3.0.0-pre.40). There are no new breaking changes, so this will not reset our release clock for 3.0.0 (which should be in about a week). xunit.net/releases/v3/... #DotNet #CSharp #FSharp #UnitTest #TDD

We updated the API documentation pages to include a version home page which includes a list of commonly used types. api.xunit.net What do you think about the type list? Things you would add/remove?

A prototype of the new web site is live at new.xunit.net. The only thing missing from this is integrating the API content, which we're working on before we ship 3.0 (at which point we'll have the new site live). Please poke and prod and let us know what's broken!

We just shipped a new prerelease build of the core framework (3.0.0-pre.25). This includes new breaking changes since last week's prerelease. Please check the release notes for more information. xunit.net/releases/v3/... #DotNet #CSharp #FSharp #UnitTest #TDD

We just shipped prerelease builds of core framework (3.0.0-pre.15) and analyzers (1.23.0-pre.3). This is a major version update with breaking changes. Check the release notes for more information. xunit.net/releases/v3/... xunit.net/releases/ana... #DotNet #CSharp #FSharp #UnitTest #TDD

We just shipped core framework v3 2.0.3, analyzers 1.22.0, and Visual Studio adapter 3.1.1. Check the release notes for new features and bugs fixed. xunit.net/releases/v3/... xunit.net/releases/ana... xunit.net/releases/vis... #DotNet #CSharp #FSharp #UnitTest #TDD

For 3.0.0, we will be shipping at least one prerelease version, to be able to collect feedback on (and give time to evaluate the impact of) the breaking changes. In retrospect, we should have done this for 2.0.0. This will be the policy going forward. #DotNet #CSharp #FSharp

We just shipped core framework v3 2.0.2 and Visual Studio adapter 3.1.0. Check the release notes for new features and bugs fixed. Note: The Visual Studio adapter has moved up to .NET 8 (from .NET 6). xunit.net/releases/v3/... xunit.net/releases/vis... #DotNet #CSharp #FSharp #UnitTest #TDD

We have a prototype of the API documentation online: api.xunit.net We're not sure if it will live on a separate URL forever, but until the main site is rebuilt with DocFX, this is how it has to be for now. Feedback welcome! #DotNet #UnitTest #TDD

We just shipped core framework v3 2.0.1 and source analyzers 1.21.0. Check the release notes for new features and bugs fixed. xunit.net/releases/v3/... xunit.net/releases/ana... #DotNet #CSharp #FSharp #UnitTest #TDD

We just shipped core framework v3 2.0.0. This contains breaking changes, so the release notes are rather more detailed than normal. Release notes: xunit.net/releases/v3/... #DotNet #CSharp #FSharp #UnitTest #TDD

The next release will be 2.0.0, so today we're merging the `rel/v3-2.0.0` branch into `main`. Hopefully that release will be in about a week. 🤞

More thoughts about test parallelism as it involves the starting/finished message pairs for test collections, test classes, and test methods. If you're a runner author, do you use these messages? Can we just remove them? Provide thoughts here: github.com/xunit/xunit/... #DotNet #UnitTest

With the release of VS 2022 17.13, you may notice Test Explorer behaves slightly differently with your v3 test projects. That's because they have enabled Microsoft.Testing.Platform preview features by default. If you have issues, you can uncheck this box to revert back. #DotNet

Thinking about what an AOT version of v3 would look like. Brad spent some time talking to Andy Gocke last year about it. It almost surely end up being a completely separate code base/package. No mixing and matching, because the internal design would be very different. 1/5

We are considering changing some of the options for the ways tests run in parallel against one another. Please read this and add your thoughts. Thanks! github.com/xunit/xunit/... #DotNet #UnitTest

We'd like to get some feedback on a change coming in 2.0.0 for Assert.Equal displays when doing collection comparisons. We've already made a change to make string comparisons better, but should we do it for all collection values? github.com/xunit/xunit/... #DotNet #UnitTest