Table of Contents

Core Framework v3 4.0.3 2026 November 8

Today, we're shipping three new releases:

  • xUnit.net Core Framework v3 4.0.3
  • xUnit.net Analyzers 2.3.0 (release notes)

It's been 4 weeks since the release of 4.0.2.

As always, we'd like to thank all the users who contributed to the success of xUnit.net through usage, feedback, and code. 🎉

Release Notes

These release notes are a list of changes from 4.0.2 to 4.0.3.

Core Framework

  • BUG: We have fixed an issue where the crash detection logic could incorrect claim a test process crashed prematurely. xunit/xunit#3656

  • BUG: We have fixed an issue which incorrectly reported interface methods are "invalid overloads" of a test method when using an interface as a "test implementation template". xunit/xunit#3655

Assertion Library

  • We have added support for properly displaying DateOnly values in theory values. xunit/xunit#3653

Native AOT

  • BUG: We have fixed an issue with assembly fixture registration that was causing compile failures. This affected [assembly: AssemblyFixture] as well as [assembly: CaptureConsole] and [assembly: CaptureTrace], which piggyback onto the assembly fixture registration system.

Runners

  • BUG: We have fixed an issue where some results files could either get corrupted or not be generated at all when they contained invalid JSON or XML. xunit/xunit#3651

Microsoft Testing Platform

  • We have improved the argument validation logic so that all errors are reported correctly before the system tries to run the tests. We have also updated several validation messages to be clearer about which switch and value are causing the validation failure. xunit/xunit#3654

  • We have overhauled the way cleanup failures are reported to Microsoft Testing Platform. Test cleanup failures and test case cleanup failures will be reported against the test case to which they belong as an additional failure (in addition to any existing results for that test case); all other cleanup failures will be reported as additional failures for all test cases in which they could be affected (for example, a test class cleanup failure will be reported as a failure for all test cases that are associated with the test class). Note that this behavior differs from our first party support for cleanup failures, will reports them as separate "errors", a concept which is not available via Microsoft Testing Platform. xunit/xunit#3660

  • The Microsoft Testing Platform v2 packages have been updated to version 2.5.2.

Edit this page