xUnit.net

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.

346 followers1 following152 posts

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.

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

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.comReconsider NuGet deprecation flag for xUnit.net v2 · Issue #3486 · xunit/xunitHi 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...

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.

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

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.

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.

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

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.comDownload .NET (Linux, macOS, and Windows) | .NETFree downloads for building and running .NET apps on Linux, macOS, and Windows. Runtimes, SDKs, and developer packs for .NET Framework, .NET, and ASP.NET.

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