"The MSTest framework can be accessed via NuGet. With MSTest 3.4, support for WinUI framework applications is added to MSTest.Runner. With this improvement, a project sample is offered and work is under way to simplify testing of unpackaged WinUI applications. Microsoft also has improved the test runner's performance by using built-in System.Text.Json for .NET rather than Jsonite and by caching command line options."
"The rules are intended to ensure correct use of assertions and attributes, help enforce design preferences, and offer other improvements. Also in MSTest 3.4, Microsoft has fixed a longstanding request to support STA threads in MSTest for VSTest and MSTest.Runner for all supported target frameworks. Plans call for improving the experience by having some specific tests or test classes run in STA thread mode."
"Microsoft also has introduced the ability to define timeouts on fixture methods, such as AssemblyInitiative, AssemblyCleanup, ClassCleanup, and TestCleanup. This provides more control over test execution. Microsoft also has added [Timeout] support to all fixture methods in MSTest 3.4, including initialize and cleanup methods. Also added was STA thread support for UI tests. Both were issues reported by users and the community."
MSTest 3.4 introduces WinUI framework support in MSTest.Runner with a sample project and work to simplify testing of unpackaged WinUI applications. The test runner performance improves by switching to System.Text.Json and caching command-line options. MSTest.Analyzers adds nine Roslyn rules to enforce assertion and attribute usage, design preferences, and reduce common pitfalls. STA thread support for VSTest and MSTest.Runner is implemented across supported frameworks, with plans to run select tests or classes in STA mode. Fixture methods now support configurable timeouts, and UI testing, Playwright/Aspire boilerplate, and SDK usage have been simplified with enhanced samples.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]