Releases: microsoft/testfx
v3.0.0-preview-20221110-04
See the release notes here.
Breaking changes
See breaking changes announcement
- Following Microsoft .NET lifecycle
- Dropped support for .NET Framework 4.5 (moved to 4.6.2)
- Dropped support for .NET Standard 1.0 (moved to 2.0)
- Dropped support for UWP before 16299
- Dropped support for WinUI before 18362
- Dropped support for .NET 5 (replaced with netcoreapp3.1 and .NET 6)
- Merge timeout behaviors across all target frameworks
- Change available constructors for
DataRowAttribute - Change test ID generation strategy (allow to switch to previous strategies)
v2.3.0-preview-20220810-02
See release notes here.
v2.2.10
v2.2.10-preview-20220414-01
See release notes here.
v2.2.9
Parallel output
🙇 Shout out to @SimonCropp, for bringing this functionality to XUnit in his https://github.com/SimonCropp/XunitContext project. And being an inspiration for implementing this.
MSTest 2.2.9 captures all Console output and attaches it to the correct test, even if you are running tests in parallel. This output is captured from your test code as well as from the tested code. And it requires no special setup.
Before
In 2.2.8, test output is scattered among tests, in our example, one unlucky test gets all the output of other tests just mixed together:
After
With 2.2.9, each output is correctly attached to the test that produced it:
Also notice that we are also capturing debug, trace and error. And we are not awaiting the FastChild method, and the output is still assigned correctly. Souce code.
Limitations
Due to the way that class and assembly initialize, and cleanup are invoked, their output will end up in the first test that run (or last for cleanup). This is unfortunately not easily fixable.
See release notes here.
