-
Notifications
You must be signed in to change notification settings - Fork 6k
Add docs for tpv0 removal #48173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Add docs for tpv0 removal #48173
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
@@ -0,0 +1,61 @@ | ||||||||||||||||||||
--- | ||||||||||||||||||||
title: MSTest migration from Legacy Test runner | ||||||||||||||||||||
description: Learn about migrating from Legacy test runner to latest MSTest. | ||||||||||||||||||||
author: nohwnd | ||||||||||||||||||||
ms.author: jajares | ||||||||||||||||||||
ms.date: 08/21/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. | ||||||||||||||||||||
|
||||||||||||||||||||
### Who is impacted? | ||||||||||||||||||||
|
||||||||||||||||||||
Users who upgrade to VSTest 18.0.0 or newer and encounter error: | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||||||
|
||||||||||||||||||||
```plaintext | ||||||||||||||||||||
MSTest v1 run was offloaded to legacy TestPlatform runner, this is typically caused by: | ||||||||||||||||||||
- using .testsettings file | ||||||||||||||||||||
- setting ForcedLegacyMode in your runsettings file | ||||||||||||||||||||
- running Web and Load test (WLT) | ||||||||||||||||||||
- running Coded UI Tests (CUIT) | ||||||||||||||||||||
- running manual tests | ||||||||||||||||||||
- running generic tests | ||||||||||||||||||||
|
||||||||||||||||||||
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 Visual Studio. | ||||||||||||||||||||
|
||||||||||||||||||||
### Solving the error | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||||||
|
||||||||||||||||||||
The error can show up for multiple reasons, typically the reasons that are listed. | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||||||
|
||||||||||||||||||||
#### Using .testsettings file | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||||||
|
||||||||||||||||||||
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. | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
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). | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||||||
|
||||||||||||||||||||
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). | ||||||||||||||||||||
|
||||||||||||||||||||
#### Setting ForcedLegacyMode in runsettings | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||||||
|
||||||||||||||||||||
Inspect your runsettings file to see if `<ForcedLegacyMode>true</ForcedLegacyMode>` is set explicitly. This will force switching to the legacy MSTest runner. You need to remove this explicit setting. | ||||||||||||||||||||
|
||||||||||||||||||||
#### Running Web and Load test (WLT) | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
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. | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||||||
|
||||||||||||||||||||
#### Running Coded UI Tests (CUIT) | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
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. | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||||||
|
||||||||||||||||||||
#### Running manual tests | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
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. | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||||||
|
||||||||||||||||||||
#### Generic tests tests | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
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. | ||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.