Add docs for tpv0 removal #48173
Open
Add docs for tpv0 removal #48173
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dotnet-policy-service
bot
added
dotnet-fundamentals/svc
community-contribution
|
Adding @gewarren as a reviewer as this is related to breaking changes in the product. |
gewarren
approved these changes
Sep 3, 2025
|
|
||
| # MSTest legacy runner migration guide | ||
|
|
||
| This guide assists users in upgrading their MSTest tests that rely on legacy test runner in Visual Studio and VSTest, to move to latest MSTest. |
There was a problem hiding this comment.
Suggested change
| This guide assists users in upgrading their MSTest tests that rely on legacy test runner in Visual Studio and VSTest, to move to latest MSTest. | |
| This guide assists you in upgrading your MSTest tests that rely on legacy test runner in Visual Studio and VSTest to the latest MSTest. |
|
|
||
| ### Who is impacted? | ||
|
|
||
| Users who upgrade to VSTest 18.0.0 or newer and encounter error: |
There was a problem hiding this comment.
Suggested change
| Users who upgrade to VSTest 18.0.0 or newer and encounter error: | |
| If you upgrade to VSTest 18.0.0 or later and encounter error the following error, you need to migrate: |
|
|
||
| ### Solving the error | ||
|
|
||
| The error can show up for multiple reasons, typically the reasons that are listed. |
There was a problem hiding this comment.
Suggested change
| The error can show up for multiple reasons, typically the reasons that are listed. | |
| The error can appear for multiple reasons: | |
| - [Using a .testsettings file](#using-a-testsettings-file) | |
| - [Setting ForcedLegacyMode](#setting-forcedlegacymode) | |
| - [Web and Load tests (WLT)](web-and-load-tests-wlt) | |
| - [Coded UI tests (CUIT)](#coded-ui-tests-cuit) | |
| - [Manual tests](#manual-tests) | |
| - [Generic tests](#generic-tests) |
|
|
||
| Version 18 of VSTest removed the ability to run MSTest v1 tests via the legacy runner (running MSTest v1 tests via VSTest remains unaffected.). The legacy runner, also called TMI, TPv0, QTAgent, was removed from VSTest and Visual Studio. | ||
|
|
||
| ### Solving the error |
There was a problem hiding this comment.
Suggested change
| ### Solving the error | |
| ### Resolve the error |
|
|
||
| The error can show up for multiple reasons, typically the reasons that are listed. | ||
|
|
||
| #### Using .testsettings file |
There was a problem hiding this comment.
Suggested change
| #### Using .testsettings file | |
| #### Using a .testsettings file |
|
|
||
| Providing `.testsettings` file to the run will trigger this error. Test settings files are no longer supported in VSTest and you should replace them with `.runsettings` file. | ||
|
|
||
| To migrate from testsettings to runsettings, you can use the TestSettings migrator tool that is shipped with Visual Studio 2022. For more information, see [Upgrade from .testsettings to .runsettings](https://learn.microsoft.com/visualstudio/test/migrate-testsettings-to-runsettings). |
There was a problem hiding this comment.
Suggested change
| To migrate from testsettings to runsettings, you can use the TestSettings migrator tool that is shipped with Visual Studio 2022. For more information, see [Upgrade from .testsettings to .runsettings](https://learn.microsoft.com/visualstudio/test/migrate-testsettings-to-runsettings). | |
| To migrate from testsettings to runsettings, you can use the TestSettings migrator tool that shipped with Visual Studio 2022. For more information, see [Upgrade from .testsettings to .runsettings](/visualstudio/test/migrate-testsettings-to-runsettings). |
|
|
||
| #### Running Web and Load test (WLT) | ||
|
|
||
| Web and Load test workload and adapter was deprecated and removed. If you still have the need to run Web and Load tests, avoid upgrading from VSTest 17.x. |
There was a problem hiding this comment.
Suggested change
| Web and Load test workload and adapter was deprecated and removed. If you still have the need to run Web and Load tests, avoid upgrading from VSTest 17.x. | |
| The Web and Load test workload and adapter was deprecated and removed. If you still need to run Web and Load tests, avoid upgrading from VSTest 17.x. |
|
|
||
| #### Running Coded UI Tests (CUIT) | ||
|
|
||
| Coded UI test workload and adapter was deprecated and removed. If you still have the need to run Coded UI tests, avoid upgrading from VSTest 17.x. |
There was a problem hiding this comment.
Suggested change
| Coded UI test workload and adapter was deprecated and removed. If you still have the need to run Coded UI tests, avoid upgrading from VSTest 17.x. | |
| The Coded UI test workload and adapter was deprecated and removed. If you still need to run Coded UI tests, avoid upgrading from VSTest 17.x. |
|
|
||
| #### Running manual tests | ||
|
|
||
| Manual test test type was deprecated and removed. If you still have the need to manual tests, avoid upgrading from VSTest 17.x. |
There was a problem hiding this comment.
Suggested change
| Manual test test type was deprecated and removed. If you still have the need to manual tests, avoid upgrading from VSTest 17.x. | |
| The manual-test test type was deprecated and removed. If you still need to run manual tests, avoid upgrading from VSTest 17.x. |
|
|
||
| #### Generic tests tests | ||
|
|
||
| Generic test test type was deprecated and removed. If you still have the need to manual tests, avoid upgrading from VSTest 17.x. |
There was a problem hiding this comment.
Suggested change
| Generic test test type was deprecated and removed. If you still have the need to manual tests, avoid upgrading from VSTest 17.x. | |
| The generic-test test type was deprecated and removed. If you still need to run generic tests, avoid upgrading from VSTest 17.x. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds short doc that is linked from the error shown when tpv0 is used in VSTest 18. The component was removed and this doc will help dispatching the users to migration documents, especially mstest v1 to mstest v3 where we expect the most "traffic". This is also a place that we can update with additional FAQ etc as more people encounter this error.
Internal previews