Add docs for tpv0 removal #48057
Open
Add docs for tpv0 removal #48057
+61
−0
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
Youssef1313
reviewed
Aug 27, 2025
| This runner was removed from the product and can no longer be used. | ||
| ``` | ||
|
|
||
| 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 VisualStudio. |
There was a problem hiding this comment.
Suggested change
| 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 VisualStudio. | |
| 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. |
Youssef1313
reviewed
Aug 27, 2025
|
|
||
| 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 run settings you can use the TestSettings migrator tool that is shipped with VisualStudio 2022. See <https://learn.microsoft.com/visualstudio/test/migrate-testsettings-to-runsettings?view=vs-2022> |
There was a problem hiding this comment.
Suggested change
| To migrate from testsettings to run settings you can use the TestSettings migrator tool that is shipped with VisualStudio 2022. See <https://learn.microsoft.com/visualstudio/test/migrate-testsettings-to-runsettings?view=vs-2022> | |
| 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). |
Youssef1313
reviewed
Aug 27, 2025
|
|
||
| To migrate from testsettings to run settings you can use the TestSettings migrator tool that is shipped with VisualStudio 2022. See <https://learn.microsoft.com/visualstudio/test/migrate-testsettings-to-runsettings?view=vs-2022> | ||
|
|
||
| When moving away from testsettings, please also consider upgrading from MSTest v1 to latest MSTest following [this migration guide](unit-testing-mstest-migration-from-v1-to-v3.md). |
There was a problem hiding this comment.
Suggested change
| When moving away from testsettings, please also consider upgrading from MSTest v1 to latest MSTest following [this migration guide](unit-testing-mstest-migration-from-v1-to-v3.md). | |
| When moving away from testsettings, consider upgrading from MSTest v1 to latest MSTest following [this migration guide](unit-testing-mstest-migration-from-v1-to-v3.md). |
gewarren
reviewed
Aug 27, 2025
There was a problem hiding this comment.
The new file should be added to the TOC somewhere too. Otherwise it will be deleted as an "orphan".
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