Vstest Versions Save

Visual Studio Test Platform is the runner and engine that powers test explorer and vstest.console.

v17.8.0-preview-23424-02

9 months ago

What's Changed

New Contributors

Full Changelog: https://github.com/microsoft/vstest/compare/v17.8.0-preview-23371-04...v17.8.0-preview-23424-02

v17.7.2

9 months ago

What's Changed

Full Changelog: https://github.com/microsoft/vstest/compare/v17.7.1...v17.7.2

v17.7.1

9 months ago

What's Changed

  • Take System dlls from testhost folder to fix running .NET Framework dlls on mono and under VS on Mac in #4610 by @Evangelink
  • Fix hangs in parallel execution and discovery in #4629 by @nohwnd
  • Fix executable bitness for testhost.x86 in #4654 by @nohwnd

Full Changelog: https://github.com/microsoft/vstest/compare/v17.7.0...v17.7.1

v17.7.0

9 months ago

⚠️ Microsoft.TestPlatform 17.7.0 nuget package is hidden from Nuget.org, we've encountered an unexpected issue with versioning which prevents it from being used in all AzDO clients. We are working on a fix.

The most pressing issues were all backported to 17.6.1, 17.6.2 and 17.6.3.

Issues fixed (since 17.6.3)

  • Don't print socket transport error in console by @nohwnd in #4493 which fixes #4461 When testhost crashes, we no longer print the transport error:

    --> System.Exception: Unable to read data from the transport connection: 
	An existing connection was forcibly closed by the remote host..

    This error is a side-effect or our architecture is almost never the culprit. Instead it leads developers away from the actual issue which is crash of testhost, or datacollector.

  • Pass workloads to proxy managers in #4422 by @nohwnd Which allows datacollector users to only receive the sources that are currently running in the testhost associated to datacollector, instead of all the sources that have the same target framework.

  • Fix Newtonsoft versions in testhost.deps.json in #4367 by @nohwnd testhost.runtimeconfig.json files that we ship with testhost contained an old version of Newtonsoft.Json. The version in this file does not have an effect on execution, but some compliance tools statically analyze it and report possible vulnerabilities.

Other fixes:

  • Replacing calls to BuildMultipleAssemblyPath when passing only one source in acceptance tests in #4358 by @daveMueller
  • Check for null Path in #4391 by @lewing
  • Remove unused variable in #4425 by @mthalman
  • Fix execution gets stucks on single netstandard source by @nohwnd in #4497 which fixes #4392
  • TestObject use ConcurrentDictionary instead of Dictionary in #4450 by @Evangelink
  • Drop usage of Microsoft.Internal.TestPlatform.Remote in #4456 by @Evangelink

Special thanks to @SimonCropp for the many fixes regarding nullability spelling and code style in #4518, #4520, #4525, #4526, #4521, #4519, #4522, #4529 🙇

Full Changelog: https://github.com/microsoft/vstest/compare/v17.6.3...v17.7.0

Drops

  • Microsoft.TestPlatform.ObjectModel : v17.7.0

v17.8.0-preview-23371-04

9 months ago

Issues Fixed

  • Take System dlls from testhost folder #4610
  • Simplify naming in ExecutionTests
  • Fix XmlException when writing Html log with certain test names #4576

Full Changelog: here

Drops

v17.7.0-preview-23364-03

10 months ago

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

11 months ago

Issues Fixed

  • [rel/17.6] Update version to 17.6.3 by @nohwnd in #4555
  • [rel/17.6] Disable pre-start of testhosts by @nohwnd in #4554

Full Changelog: https://github.com/microsoft/vstest/compare/v17.6.2...v17.6.3

Artifacts

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

v17.7.0-preview.23280.1

11 months ago

⚠️ 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

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.

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

New Contributors

Full Changelog: https://github.com/microsoft/vstest/compare/v17.6.0...v17.7.0-preview.23280.1

v17.6.2

11 months ago

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: https://github.com/microsoft/vstest/issues/4516

Full Changelog: https://github.com/microsoft/vstest/compare/v17.6.1...v17.6.2

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

v17.6.1

1 year ago

Issues Fixed

This is a tiny patch to fixup few latest issues,

  • Fix no-suitable provider found by @nohwnd in https://github.com/microsoft/vstest/pull/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 https://github.com/microsoft/vstest/pull/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 https://github.com/microsoft/vstest/pull/4500 which fixes #4409

Internal updates:

Full Changelog: https://github.com/microsoft/vstest/compare/v17.6.0...v17.6.1

Artifacts

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