xUnit.net

@xunit.net

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.

For those developers who are using testconfig.json, we'll be adding a JSON schema with tomorrow's release of v3 4.0.2.

We will release 4.0.2 in a few days, following our typical monthly release cadence. Please make sure to get bugs reported soon if you want their fixes included in the next release. Thanks!

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

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!

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

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

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%

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

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

dotnet.social

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

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

github.com

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.