Skip to content

Releases: microsoft/vstest

v17.7.0-preview-23364-03

16 Jul 19:26
bc17bb9
Compare
Choose a tag to compare
Pre-release

Issues Fixed

  • Trim away netframework targets in source-build #4357
  • Re-enable publishing nugets, don't continue on error #4356
  • Merged PR 30352: arcade into main
  • Merged PR 29591: Onboard to arcade

Full Changelog: here

Drops

v17.6.3

27 Jun 11:51
e7ea853
Compare
Choose a tag to compare

Issues Fixed

Full Changelog: v17.6.2...v17.6.3

Artifacts

  • TestPlatform vsix: 17.6.3
  • Microsoft.TestPlatform.ObjectModel : 17.6.3

v17.6.2

06 Jun 13:26
911a038
Compare
Choose a tag to compare

Fixes

This patch addresses the problems that were introduced in 17.6.0 that happen when running on AzDo with the default test.dll filter, which includes additional TestPlatform dlls into the run and fails it.

To mitigate this issue we solved the bug in 17.6.1, and added additional exclusions for known assemblies that are coming from TestPlatform and commonly used test adapters, to avoid trying to run tests from those assemblies.

Description and workarounds for this issue are available here: #4516

  • [rel/17.6] Downgrade Nuget.Frameworks to 6.5.0 by @nohwnd in #4512
  • [rel/17.6] Filter out known platform sources by @nohwnd in #4517
  • [rel/17.6] Exclude also known resource dlls by @Evangelink in #4528

Full Changelog: v17.6.1...v17.6.2

Artifacts
TestPlatform vsix: 17.6.2
Microsoft.TestPlatform.ObjectModel : 17.6.2

v17.6.1

01 Jun 15:24
5121d9f
Compare
Choose a tag to compare

Issues Fixed

This is a tiny patch to fixup few latest issues,

  • Fix no-suitable provider found by @nohwnd in #4474 which fixes #4467

    When .NET Portable or .NET Standard dlls are provided to the run, the run crashes with "No suitable test runtime provider was found", which is a regression introduced in 17.6.0.

  • Fix hangdump running into crashdump by @nohwnd in #4480 which fixes #4378

    Running --blame-hang and --blame-crash at the same time, can result in --blame-hang cancelling --blame-crash, and killing the testhost in the process, resulting in no dumps being created. This fix waits for --blame-crash to finish dumping the process, and then it creates hang dump.

  • Update Nuget.Frameworks by @nohwnd in #4500 which fixes #4409

Internal updates:

Full Changelog: v17.6.0...v17.6.1

Artifacts

  • TestPlatform vsix: 17.6.1
  • Microsoft.TestPlatform.ObjectModel : 17.6.1

v17.7.0-preview.23280.1

12 Jun 16:40
94103c3
Compare
Choose a tag to compare
Pre-release

⚠️ This version of Microsoft.TestPlatform nuget was unlisted on Nuget.org, because it causes issues when running tests in AzureDevOps, when VSTest installer is used, and configured to pick up the latest preview version (#4544).


What is new since 17.6.0?

Version 17.7.0 was filled with moving our infrastructure to build via Arcade, which brought us a more unified build experience and better cooperation with other teams in dotnet organization.

This migration brought a major change to our versioning of preview packages, which will no longer follow the 17.6.0-preview-20230223-05 (<version>-preview<date>-<build>).

Fixes

  • Don't print socket transport error in console by @nohwnd in #4493

When test run aborts we are no longer printing the connection related error:

System.Exception: One or more errors occurred.
 ---> System.Exception: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
 ---> System.Exception: An existing connection was forcibly closed by the remote host.
   at System.Net.Sockets.NetworkStream.Read(Span`1 buffer)

This error is a common source of confusion, and is not actionable for the user. It simply means that testhost crashed, and the testhost error follows after it, or that logs need to be inspected.

When both --blame-hang and --blame-crash are specified on Windows, and hang dump is triggered then stopping ProcDump is subject to a race condition. Stopping ProcDump too early causes testhost to crash and no dump (nor the hang dump or the crash dump) is generated. This release fixes this issue by waiting for crash dump to finish.

  • Fix no-suitable provider found by @nohwnd in #4475
  • Fix execution gets stucks on single netstandard source by @nohwnd in #4497

Regressions from 17.5.0 causing crashes of TestHost when .NET Standard dlls, or TestPlatform own dlls are provided for run are fixed, and a list of dlls that are known platform dlls are excluded.

Data collectors consuming the dlls that are run are now provided only paths to dlls that the current testhost is running, rather than all dlls that were provided to the run.

Additional fixes

  • Check for null Path by @lewing in #4391
  • Fix Newtonsoft versions in testhost.deps.json by @nohwnd in #4367
  • Replacing calls to BuildMultipleAssemblyPath when passing only one source in acceptance tests by @daveMueller in #4358
  • Deprecate serialization ctor for .NET8 onward by @Evangelink in #4440
  • Fix TestObject use ConcurrentDictionary instead of Dictionary by @Evangelink in #4450

New Contributors

Full Changelog: v17.6.0...v17.7.0-preview.23280.1

v17.6.0

16 May 13:39
Compare
Choose a tag to compare

See the release notes here.

v17.3.3

24 Mar 13:34
Compare
Choose a tag to compare

See the release notes here.

v17.2.1

24 Mar 12:54
Compare
Choose a tag to compare

See the release notes here.

v17.0.2

24 Mar 11:47
Compare
Choose a tag to compare

See the release notes here.

v17.6.0-preview-20230223-05

13 Mar 14:49
05c0c4c
Compare
Choose a tag to compare
Pre-release

See the release notes here.