Replace MSTest Runner with Microsoft Testing Platform (#45099)

* Replace MSTest Runner with Microsoft Testing Platform

* merge

* Update msbuild-props

* Update docs

* Undo some changes

* Update docs/core/testing/unit-testing-mstest-sdk.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/testing/unit-testing-mstest-sdk.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/testing/unit-testing-mstest-sdk.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/testing/unit-testing-mstest-sdk.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/testing/unit-testing-mstest-sdk.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/testing/unit-testing-mstest-sdk.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/testing/unit-testing-platform-vs-vstest.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/testing/unit-testing-mstest-runner-intro.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/testing/unit-testing-mstest-runner-intro.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/testing/unit-testing-mstest-runner-intro.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/testing/unit-testing-mstest-runner-intro.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/testing/unit-testing-mstest-runner-intro.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/project-sdk/msbuild-props.md

Co-authored-by: Youssef Victor <[email protected]>

* Update docs/core/project-sdk/msbuild-props.md

Co-authored-by: Youssef Victor <[email protected]>

* Use Microsoft.Testing.Platform in mstest runner intro

* Update link

* Remove MTP from fsharp and vb

* Fix links

---------

Co-authored-by: Youssef Victor <[email protected]>

Author: mariam-abdulla

docs/core/project-sdk/msbuild-props.md

@@ -1556,11 +1556,11 @@ When you use the [MSTest project SDK](../testing/unit-testing-mstest-sdk.md), th
 | `None`         | No extensions are enabled.                                                                    |
 | `AllMicrosoft` | Enable all extensions shipped by Microsoft (including extensions with a restrictive license). |
 
-For more information, see [MSTest runner profile](../testing/unit-testing-mstest-sdk.md#mstest-runner-profile).
+For more information, see [Microsoft.Testing.Platform profile](../testing/unit-testing-mstest-sdk.md#microsofttestingplatform-profile).
 
 ### UseVSTest
 
-Set the `UseVSTest` property to `true` to switch from the MSTest runner to the [VSTest](/visualstudio/test/vstest-console-options) runner when using the [MSTest project SDK](../testing/unit-testing-mstest-sdk.md).
+Set the `UseVSTest` property to `true` to switch from Microsoft.Testing.Platform to the [VSTest](/visualstudio/test/vstest-console-options) runner when using the [MSTest project SDK](../testing/unit-testing-mstest-sdk.md).
 
 ### MSTestAnalysisMode
 

docs/core/testing/microsoft-testing-platform-vs-vstest.md

@@ -8,7 +8,7 @@ ms.date: 12/15/2023
 
 # Microsoft.Testing.Platform and VSTest comparison
 
-`Microsoft.Testing.Platform` is a lightweight and portable alternative to [VSTest](https://github.com/microsoft/vstest) for running tests in command line, in continuous integration (CI) pipelines, in Visual Studio Test Explorer, and in Visual Studio Code. In this article, you learn the key differences between the MSTest runner and VSTest.
+`Microsoft.Testing.Platform` is a lightweight and portable alternative to [VSTest](https://github.com/microsoft/vstest) for running tests in command line, in continuous integration (CI) pipelines, in Visual Studio Test Explorer, and in Visual Studio Code. In this article, you learn the key differences between Microsoft.Testing.Platform and VSTest.
 
 ## Differences in test execution
 

docs/core/testing/unit-testing-fsharp-with-mstest.md

@@ -56,7 +56,7 @@ Make the *MathService.Tests* directory the current directory and create a new pr
 </ItemGroup>
 ```
 
-The test project requires other packages to create and run unit tests. `dotnet new` in the previous step added MSTest and the MSTest runner. Now, add the `MathService` class library as another dependency to the project. Use the `dotnet add reference` command:
+The test project requires other packages to create and run unit tests. `dotnet new` in the previous step added MSTest. Now, add the `MathService` class library as another dependency to the project. Use the `dotnet add reference` command:
 
 ```dotnetcli
 dotnet add reference ../MathService/MathService.fsproj

docs/core/testing/unit-testing-mstest-runner-intro.md

@@ -12,11 +12,11 @@ MSTest supports running tests with both VSTest and [Microsoft.Testing.Platform (
 
 The MSTest runner is open source and builds on the [`Microsoft.Testing.Platform`](./microsoft-testing-platform-intro.md) library. You can find `Microsoft.Testing.Platform` code in the [microsoft/testfx](https://github.com/microsoft/testfx/tree/main/src/Platform/Microsoft.Testing.Platform) GitHub repository. The MSTest runner comes bundled with `MSTest in 3.2.0` or newer.
 
-## Enable MSTest runner in an MSTest project
+## Enable Microsoft.Testing.Platform in an MSTest project
 
-It's recommended to use [MSTest SDK](./unit-testing-mstest-sdk.md) as it greatly simplifies your project configuration and updating the project, and it ensures a proper alignment of the versions of the platform (MSTest runner) and its extensions.
+It's recommended to use [MSTest SDK](./unit-testing-mstest-sdk.md) as it greatly simplifies your project configuration and updating the project, and it ensures a proper alignment of the versions of the platform (Microsoft.Testing.Platform) and its extensions.
 
-When you use `MSTest SDK`, by default you're opted in to using MSTest runner.
+When you use `MSTest SDK`, by default you're opted in to using Microsoft.Testing.Platform.
 
 ```xml
 <Project Sdk="MSTest.Sdk/3.8.2">
@@ -38,7 +38,7 @@ Consider the following example project file:
 <Project Sdk="Microsoft.NET.Sdk">
 
   <PropertyGroup>
-    <!-- Enable the MSTest runner, this is an opt-in feature -->
+    <!-- Enable Microsoft.Testing.Platform, this is an opt-in feature -->
     <EnableMSTestRunner>true</EnableMSTestRunner>
     <TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport>
 
@@ -70,7 +70,7 @@ Consider the following example project file:
     <PackageReference Include="MSTest" Version="3.8.0" />
 
     <!--
-      Coverlet collector isn't compatible with MSTest runner, you can
+      Coverlet collector isn't compatible with Microsoft.Testing.Platform, you can
       either switch to Microsoft CodeCoverage (as shown below),
       or switch to be using coverlet global tool
       https://github.com/coverlet-coverage/coverlet#net-global-tool-guide-suffers-from-possible-known-issue
@@ -89,7 +89,7 @@ Consider the following example project file:
 
 ### .runsettings
 
-The MSTest runner supports the [runsettings](microsoft-testing-platform-extensions-vstest-bridge.md#runsettings-support) through the command-line option `--settings`. For the full list of supported MSTest entries, see [Configure MSTest: Runsettings](./unit-testing-mstest-configure.md#runsettings). The following commands show various usage examples.
+Microsoft.Testing.Platform supports the [runsettings](microsoft-testing-platform-extensions-vstest-bridge.md#runsettings-support) through the command-line option `--settings`. For the full list of supported MSTest entries, see [Configure MSTest: Runsettings](./unit-testing-mstest-configure.md#runsettings). The following commands show various usage examples.
 
 Using `dotnet run`:
 

docs/core/testing/unit-testing-mstest-sdk.md

@@ -68,16 +68,16 @@ You don't need anything else to build and run your tests and you can use the sam
 
 ## Select the runner
 
-By default, MSTest SDK relies on [MSTest runner](./unit-testing-mstest-runner-intro.md), but you can switch to [VSTest](/visualstudio/test/vstest-console-options) by adding the property `<UseVSTest>true</UseVSTest>`.
+By default, MSTest SDK relies on [Microsoft.Testing.Platform](./unit-testing-mstest-runner-intro.md), but you can switch to [VSTest](/visualstudio/test/vstest-console-options) by adding the property `<UseVSTest>true</UseVSTest>`.
 
-## Extend MSTest runner
+## Extend Microsoft.Testing.Platform
 
-You can customize `MSTest runner` experience through a set of [NuGet package extensions](./microsoft-testing-platform-extensions.md). To simplify and improve this experience, MSTest SDK introduces two features:
+You can customize `Microsoft.Testing.Platform` experience through a set of [NuGet package extensions](./microsoft-testing-platform-extensions.md). To simplify and improve this experience, MSTest SDK introduces two features:
 
-- [MSTest runner profile](#mstest-runner-profile)
+- [Microsoft.Testing.Platform profile](#microsofttestingplatform-profile)
 - [Enable or disable extensions](#enable-or-disable-extensions)
 
-### MSTest runner profile
+### Microsoft.Testing.Platform profile
 
 The concept of *profiles* allows you to select the default set of configurations and extensions that will be applied to your test project.
 
@@ -275,7 +275,7 @@ Finally, based on the extensions profile you're using, you can also remove some
 
 ### Update your CI
 
-Once you've updated your projects, if you're using `MSTest runner` (default) and if you rely on `dotnet test` to run your tests, you must update your CI configuration. For more information and to guide your understanding of all the required changes, see [dotnet test integration](./microsoft-testing-platform-integration-dotnet-test.md#dotnet-test---microsofttestingplatform-mode).
+Once you've updated your projects, if you're using `Microsoft.Testing.Platform` (default) and if you rely on `dotnet test` to run your tests, you must update your CI configuration. For more information and to guide your understanding of all the required changes, see [dotnet test integration](./microsoft-testing-platform-integration-dotnet-test.md#dotnet-test---microsofttestingplatform-mode).
 
 Here's an example update when using the `DotNetCoreCLI` task in Azure DevOps:
 

docs/core/testing/unit-testing-visual-basic-with-mstest.md

@@ -61,7 +61,7 @@ Make the *PrimeService.Tests* directory the current directory and create a new p
 </ItemGroup>
 ```
 
-The test project requires other packages to create and run unit tests. `dotnet new` in the previous step added MSTest and the MSTest runner. Now, add the `PrimeService` class library as another dependency to the project. Use the [`dotnet add reference`](../tools/dotnet-add-reference.md) command:
+The test project requires other packages to create and run unit tests. `dotnet new` in the previous step added MSTest. Now, add the `PrimeService` class library as another dependency to the project. Use the [`dotnet add reference`](../tools/dotnet-add-reference.md) command:
 
 ```dotnetcli
 dotnet add reference ../PrimeService/PrimeService.vbproj

docs/core/tools/dotnet-new-sdk-templates.md

@@ -158,7 +158,7 @@ The ability to create a project for an earlier TFM depends on having that versio
    The runner/platform for the test project. The possible values are:
 
   - `VSTest` - VSTest platform (Default).
-  - `MSTest` - MSTest Runner (i.e. Microsoft.Testing.Platform).
+  - `MSTest` - Microsoft.Testing.Platform.
 
 - **`--coverage-tool <COVERAGE_TOOL>`**
 
@@ -169,7 +169,7 @@ The ability to create a project for an earlier TFM depends on having that versio
 
 - **`--extensions-profile <EXTENSIONS_PROFILE>`**
 
-  The SDK extensions profile when using MSTest Runner. The possible values are:
+  The SDK extensions profile when using Microsoft.Testing.Platform. The possible values are:
 
   - `Default` - Default extensions profile (Default).
   - `None` - No extensions are enabled.