From b03ef4fca287afa4b5d514ddaa3306b42dbfbd7f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Jare=C5=A1?= Date: Thu, 21 Aug 2025 12:21:26 +0200 Subject: [PATCH 1/6] Add docs for tmi removal --- .../unit-testing-mstest-migration-from-tmi.md | 61 +++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 docs/core/testing/unit-testing-mstest-migration-from-tmi.md diff --git a/docs/core/testing/unit-testing-mstest-migration-from-tmi.md b/docs/core/testing/unit-testing-mstest-migration-from-tmi.md new file mode 100644 index 0000000000000..1dafeac0bbd75 --- /dev/null +++ b/docs/core/testing/unit-testing-mstest-migration-from-tmi.md @@ -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: + +```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 VisualStudio. + +### Solving the error + +The error can show up for multiple reasons, typically the reasons that are listed. + +#### Using .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 run settings you can use the TestSettings migrator tool that is shipped with VisualStudio 2022. See + +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). + +#### Setting ForcedLegacyMode in runsettings + +Inspect your runsettings file to see if `true` 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) + +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. + +#### 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. + +#### 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. + +#### 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. From a6a104c8906a7ef10eabe31ec9ff27bf559f3e36 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Jare=C5=A1?= Date: Thu, 28 Aug 2025 10:21:19 +0200 Subject: [PATCH 2/6] Add to TOC --- docs/navigate/devops-testing/toc.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/navigate/devops-testing/toc.yml b/docs/navigate/devops-testing/toc.yml index 0221c6819b87b..7b07ab88687d4 100644 --- a/docs/navigate/devops-testing/toc.yml +++ b/docs/navigate/devops-testing/toc.yml @@ -75,6 +75,8 @@ items: href: ../../core/testing/unit-testing-mstest-migration-from-v1-to-v3.md - name: Migrate from MSTest v3 to MSTest v4 href: ../../core/testing/unit-testing-mstest-migration-v3-v4.md + - name: MSTest migration from Legacy Test runner + href: ../../core/testing/unit-testing-mstest-migration-from-tmi.md - name: Microsoft.Testing.Platform support (MSTest runner) href: ../../core/testing/unit-testing-mstest-runner-intro.md - name: Getting started From d711fda39ad5ddb99861152a7e92e514c1721cad Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Jare=C5=A1?= Date: Thu, 28 Aug 2025 10:42:10 +0200 Subject: [PATCH 3/6] Add youssefs suggestions --- docs/core/testing/unit-testing-mstest-migration-from-tmi.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/core/testing/unit-testing-mstest-migration-from-tmi.md b/docs/core/testing/unit-testing-mstest-migration-from-tmi.md index 1dafeac0bbd75..9e6867517a3f9 100644 --- a/docs/core/testing/unit-testing-mstest-migration-from-tmi.md +++ b/docs/core/testing/unit-testing-mstest-migration-from-tmi.md @@ -26,7 +26,7 @@ MSTest v1 run was offloaded to legacy TestPlatform runner, this is typically cau 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. +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 @@ -36,9 +36,9 @@ The error can show up for multiple reasons, typically the reasons that are liste 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 +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). -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). #### Setting ForcedLegacyMode in runsettings From 100f4085e3a3f4c6407a12bdb2ae3ec557636628 Mon Sep 17 00:00:00 2001 From: David Pine Date: Mon, 13 Oct 2025 08:34:38 -0500 Subject: [PATCH 4/6] Apply suggestions from code review Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com> --- .../unit-testing-mstest-migration-from-tmi.md | 39 +++++++++++-------- 1 file changed, 23 insertions(+), 16 deletions(-) diff --git a/docs/core/testing/unit-testing-mstest-migration-from-tmi.md b/docs/core/testing/unit-testing-mstest-migration-from-tmi.md index 9e6867517a3f9..a46e4961ca3f6 100644 --- a/docs/core/testing/unit-testing-mstest-migration-from-tmi.md +++ b/docs/core/testing/unit-testing-mstest-migration-from-tmi.md @@ -8,11 +8,11 @@ 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. +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: +If you upgrade to VSTest 18.0.0 or later and encounter error the following error, you need to migrate: ```plaintext MSTest v1 run was offloaded to legacy TestPlatform runner, this is typically caused by: @@ -28,34 +28,41 @@ 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 +### Resolve the error -The error can show up for multiple reasons, typically the reasons that are listed. +The error can appear for multiple reasons: -#### Using .testsettings file +- [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) -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. +#### Using a .testsettings 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). +Providing a `.testsettings` file to the run triggers this error. Test settings files are no longer supported in VSTest. Replace them with `.runsettings` files. + +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). 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 +#### Setting ForcedLegacyMode Inspect your runsettings file to see if `true` 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) +#### Web and Load tests (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. +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 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. +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 tests -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 tests -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. From 723ee659e75bca28e854767be923998ff91e16e5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Jare=C5=A1?= Date: Mon, 13 Oct 2025 17:52:58 +0200 Subject: [PATCH 5/6] Update docs/core/testing/unit-testing-mstest-migration-from-tmi.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/core/testing/unit-testing-mstest-migration-from-tmi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core/testing/unit-testing-mstest-migration-from-tmi.md b/docs/core/testing/unit-testing-mstest-migration-from-tmi.md index a46e4961ca3f6..3b24ee40335cf 100644 --- a/docs/core/testing/unit-testing-mstest-migration-from-tmi.md +++ b/docs/core/testing/unit-testing-mstest-migration-from-tmi.md @@ -12,7 +12,7 @@ This guide assists you in upgrading your MSTest tests that rely on legacy test r ### Who is impacted? -If you upgrade to VSTest 18.0.0 or later and encounter error the following error, you need to migrate: +If you upgrade to VSTest 18.0.0 or later and encounter the following error, you need to migrate: ```plaintext MSTest v1 run was offloaded to legacy TestPlatform runner, this is typically caused by: From 887c7a524dbd34b65b202a88f751d8ec83b388bd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Jare=C5=A1?= Date: Mon, 13 Oct 2025 17:53:07 +0200 Subject: [PATCH 6/6] Update docs/core/testing/unit-testing-mstest-migration-from-tmi.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/core/testing/unit-testing-mstest-migration-from-tmi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core/testing/unit-testing-mstest-migration-from-tmi.md b/docs/core/testing/unit-testing-mstest-migration-from-tmi.md index 3b24ee40335cf..6637430114957 100644 --- a/docs/core/testing/unit-testing-mstest-migration-from-tmi.md +++ b/docs/core/testing/unit-testing-mstest-migration-from-tmi.md @@ -34,7 +34,7 @@ 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) +- [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)