Tag: testing

MSTest.Sdk 4.5 and Microsoft.Testing.Platform 2.5 make the UWP or WinUI 3 app the test host itself. [UITestMethod] runs each test on the real dispatcher, packaged and AppContainer apps are activated by AUMID through a sidecar controller, and unpackaged WinUI finally works.

NUnit 5.0.0 makes Assert.ThrowsAsync, CatchAsync and DoesNotThrowAsync truly asynchronous. Forget the await and the assertion never runs. Here is what breaks, what the NUnit.Analyzers NUnit2059 rule catches, and the other NUnit 5 changes to check before upgrading.

Exit code 5 means MTP rejected a command-line option, not that tests are missing. Run the test exe directly to see the real error, then add the extension package or route the option per project.

MSTest 4.4.0 added Span<T> and ReadOnlySpan<T> overloads to Assert.Contains and Assert.DoesNotContain, which made ordinary array and string assertions fail with CS0121 on net8.0, net9.0, or any project below C# 14. MSTest 4.4.1, published on 2026-09-16, adds exact array overloads and constrained forwarders. Two explicit-generic call shapes still fail.

Microsoft.Extensions.AI.Evaluation.Quality 10.10.0 now marks unparseable and out-of-range quality scores as failed, and Microsoft.Extensions.AI.OpenAI 10.10.0 drops the Assistants adapter. Measured before and after on 10.9.0.

The Rider 2026.3 Early Access Program opened on September 7, 2026. Buried under rainbow brackets is the one line that changes a build: dotCover now reports coverage for TUnit tests, given Microsoft.Testing.Platform 2.3.0 and one package reference.

MSTest 4.4 moves MSTest.SourceGeneration out of experimental and aligns it with the MSTest version. Native AOT test projects pick it up with no opt-in, ReflectionFree mode can now skip runtime discovery for plain [TestMethod] and [DataRow], and five AOTSG diagnostics tell you which test shapes will not survive.

A step-by-step migration from VSTest to Microsoft.Testing.Platform 2.3.3: the OutputType Exe opt-in, the global.json runner switch, loggers becoming reporters, .runsettings becoming testconfig.json, and the exit codes that turn a green CI job red.

A step-by-step migration from xunit 2.9.3 to xunit.v3 4.0.0: package swaps, the OutputType Exe change, IAsyncLifetime returning ValueTask, the Xunit.Abstractions removal, and the CI filter syntax that silently stops matching.

Inside testWidgets the ambient clock from package:clock is already fake, but it starts at whatever wall time the test began. Pin it for a whole suite by overriding runTest on a custom AutomatedTestWidgetsFlutterBinding installed from flutter_test_config.dart. Verified on Flutter 3.44.2, clock 1.1.2, fake_async 1.3.3.