xUnit.net
@xunit.net
320 followers 1 following 96 posts
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.
Posts Media Videos Starter Packs
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.
Home | xUnit.net
xUnit.net
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.
We have unlisted the 3.2.0 preview (MTP v2) packages on NuGet. The documentation pages are still alive (though no longer linked) on the web site, though we will be deleting them at some point.
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
We are delaying our support for Microsoft Testing Platform v2 due to some technical limitations when interacting with .NET 10 SDK.

We will still support for targeting .NET 10 with our templates before it ships.
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
Core Framework v3 3.2.0-pre.5 | xUnit.net
xunit.net
xUnit.net @xunit.net · Aug 16
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
Release Notes | xUnit.net
xunit.net
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
Using CI Builds | xUnit.net
xunit.net
xUnit.net @xunit.net · Jul 29
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
xUnit.net (@[email protected])
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. #Do...
dotnet.social
xUnit.net @xunit.net · Jul 16
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
Release Notes | xUnit.net
xunit.net
xUnit.net @xunit.net · Jul 14
We are hopeful that someday Microsoft shares the private bits of DocFX that they use to make their API site seamlessly support multiple API versions, because the hacks we've had to do are pretty ugly.
xUnit.net @xunit.net · Jul 14
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
Core Framework v3 3.0.0 | xUnit.net
xunit.net
xUnit.net @xunit.net · Jul 13
FYI, we evaluated integrating api.xunit.net into the new site but it honestly made the main site performance not great due to the size of the TOC, and we wanted to retain the left nav filtering experience. As such, they're going to remain separate.
api.xunit.net
xUnit.net @xunit.net · Jul 13
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!
Home | xUnit.net
xunit.net
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
Release Notes for v3 3.0.0-pre.40 [2025 July 6]
Documentation site for the xUnit.net unit testing framework
xunit.net
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?
Screenshot of api.xunit.net showing the home page for the v3 2.0.3 API, with a list of commonly used types.
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!
Home | xUnit.net
new.xunit.net
Just a reminder that we only have roughly 10 more days of before we ship 3.0. If you've been putting off validating your tests and/or extensions with the latest prerelease, your time is running low...

#DotNet #CSharp #FSharp #UnitTest #TDD
xUnit.net @xunit.net · Jun 16
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
Release Notes for v3 3.0.0-pre.25 [2025 June 15]
Documentation site for the xUnit.net unit testing framework
xunit.net
If we make more breaking changes, we'll ship another prerelease build to NuGet (with release notes & an announcement) and then reset the clock for the final build.
In concert with `3.0.0` now becoming the `main` branch, you should only expect another NuGet prerelease build if there end up being more breaking changes. Otherwise, we will plan to ship a final `3.0.0` build on our normal schedule (about a month from now).