More updates to testing documentation (#45528)

Author: Youssef1313

docs/core/testing/microsoft-testing-platform-architecture-capabilities.md

@@ -8,7 +8,7 @@ ms.date: 07/11/2024
 
 # Microsoft.Testing.Platform capabilities
 
-In the context of the testing platform, a *capability* refers to the *potential to perform a specific action or provide specific information*. It's a means for the testing framework and extensions to *declare* their *ability* to *operate* in a certain manner or provide specific information to the *requesters*.
+In the context of Microsoft.Testing.Platform, a *capability* refers to the *potential to perform a specific action or provide specific information*. It's a means for the testing framework and extensions to *declare* their *ability* to *operate* in a certain manner or provide specific information to the *requesters*.
 
 The *requesters* can be any component involved in a test session, such as the platform, an extension, or the testing framework itself.
 
@@ -19,7 +19,7 @@ The primary objective of the capability system is to facilitate effective commun
 Let's consider a hypothetical example to demonstrate the necessity of a capability system.
 
 > [!NOTE]
-> This example is purely for illustrative purposes and isn't currently implemented within the testing platform or any testing framework.
+> This example is purely for illustrative purposes and isn't currently implemented within Microsoft.Testing.Platform or any testing framework.
 
 Imagine a situation where you have an extension that requires the testing framework to execute no more than one test at a time. Furthermore, after each test, the extension needs to know the CPU usage for that specific test.
 
@@ -28,7 +28,7 @@ To accommodate the preceding scenario, you need to inquire from the testing fram
 1. It has the capability to execute only one test at a time.
 2. It can provide information regarding the amount of CPU consumed by each test.
 
-How can the extension determine if the testing framework has the ability to operate in this mode and provide CPU usage information for a test session? In the testing platform, this capability is represented by an implementation the `Microsoft.Testing.Platform.Capabilities.ICapability` interface:
+How can the extension determine if the testing framework has the ability to operate in this mode and provide CPU usage information for a test session? In Microsoft.Testing.Platform, this capability is represented by an implementation the `Microsoft.Testing.Platform.Capabilities.ICapability` interface:
 
 ```csharp
 // Base capabilities contracts
@@ -111,7 +111,7 @@ In conclusion, let's summarize the primary aspects of the capability system:
 * It's essential for facilitating clear and stable communication between components.
 * All capabilities should inherit from `ICapability` or an interface that inherits from it, and are exposed through a collection with the `ICapabilities` interface.
 * It aids in the evolution of features without causing breaking changes. If a certain capability isn't supported, appropriate action can be taken.
-* The responsibility of designing, shipping, and documenting the usage of a capability lies with the *capability owner*. The testing platform can also *own* a capability in the same way as any other extension.
+* The responsibility of designing, shipping, and documenting the usage of a capability lies with the *capability owner*. Microsoft.Testing.Platform can also *own* a capability in the same way as any other extension.
 
 ## Framework capabilities
 

docs/core/testing/microsoft-testing-platform-architecture-extensions.md

@@ -8,9 +8,9 @@ ms.date: 07/11/2024
 
 # Microsoft.Testing.Platform extensibility
 
-The testing platform consists of a [testing framework](#test-framework-extension) and any number of [extensions](#other-extensibility-points) that can operate *in-process* or *out-of-process*.
+Microsoft.Testing.Platform consists of a [testing framework](#test-framework-extension) and any number of [extensions](#other-extensibility-points) that can operate *in-process* or *out-of-process*.
 
-As outlined in the [architecture](./microsoft-testing-platform-architecture.md) section, the testing platform is designed to accommodate a variety of scenarios and extensibility points. The primary and essential extension is undoubtedly the [testing framework](#test-framework-extension) that your tests will utilize. Failing to register this results in startup error. **The [testing framework](#test-framework-extension) is the sole mandatory extension required to execute a testing session.**
+As outlined in the [architecture](./microsoft-testing-platform-architecture.md) section, Microsoft.Testing.Platform is designed to accommodate a variety of scenarios and extensibility points. The primary and essential extension is undoubtedly the [testing framework](#test-framework-extension) that your tests will utilize. Failing to register this results in startup error. **The [testing framework](#test-framework-extension) is the sole mandatory extension required to execute a testing session.**
 
 To support scenarios such as generating test reports, code coverage, retrying failed tests, and other potential features, you need to provide a mechanism that allows other extensions to work in conjunction with the [testing framework](#test-framework-extension) to deliver these features not inherently provided by the [testing framework](#test-framework-extension) itself.
 
@@ -80,7 +80,7 @@ The test framework is the primary extension that provides the testing platform w
 
 ### Register a testing framework
 
-This section explains how to register the test framework with the testing platform. You register only one testing framework per test application builder using the `TestApplication.RegisterTestFramework` API as shown in [the testing platform architecture](./microsoft-testing-platform-architecture.md) documentation.
+This section explains how to register the test framework with the testing platform. You register only one testing framework per test application builder using the `TestApplication.RegisterTestFramework` API as shown in [Microsoft.Testing.Platform architecture](./microsoft-testing-platform-architecture.md) documentation.
 
 The registration API is defined as follows:
 

docs/core/testing/microsoft-testing-platform-diagnostics.md

@@ -6,13 +6,13 @@ ms.author: amauryleve
 ms.date: 05/30/2024
 ---
 
-# Microsoft Testing Platform diagnostics overview
+# Microsoft.Testing.Platform diagnostics overview
 
-Microsoft Testing platform analysis ("TPXXX") rules inspect your code for security, performance, design and other issues.
+Microsoft.Testing.Platform analysis ("TPXXX") rules inspect your code for security, performance, design and other issues.
 
 ## TPEXP
 
-Several APIs of Microsoft Testing Platform are decorated with the <xref:System.Diagnostics.CodeAnalysis.ExperimentalAttribute>. This attribute indicates that the API is experimental and may be removed or changed in future versions of Microsoft Testing Platform. The attribute is used to identify APIs that aren't yet stable and may not be suitable for production use.
+Several APIs of Microsoft.Testing.Platform are decorated with the <xref:System.Diagnostics.CodeAnalysis.ExperimentalAttribute>. This attribute indicates that the API is experimental and may be removed or changed in future versions of Microsoft.Testing.Platform. The attribute is used to identify APIs that aren't yet stable and may not be suitable for production use.
 
 To suppress this diagnostic with the `SuppressMessageAttribute`, add the following code to your project:
 

docs/core/testing/microsoft-testing-platform-extensions-code-coverage.md

@@ -8,7 +8,7 @@ ms.date: 04/10/2024
 
 # Code coverage extensions
 
-This article list and explains all `Microsoft Testing Platform` extensions related to the code coverage capability.
+This article lists and explains all Microsoft.Testing.Platform extensions related to the code coverage capability.
 
 You can use the code coverage feature to determine what proportion of your project's code is being tested by coded tests such as unit tests. To effectively guard against bugs, your tests should exercise or *cover* a large proportion of your code.
 

docs/core/testing/microsoft-testing-platform-extensions-diagnostics.md

@@ -8,7 +8,7 @@ ms.date: 04/10/2024
 
 # Diagnostics extensions
 
-This article list and explains all `Microsoft Testing Platform` extensions related to the diagnostics capability.
+This article lists and explains all Microsoft.Testing.Platform extensions related to the diagnostics capability.
 
 ## Built-in options
 

docs/core/testing/microsoft-testing-platform-extensions-hosting.md

@@ -8,7 +8,7 @@ ms.date: 04/10/2024
 
 # Hosting extensions
 
-This article list and explains all `Microsoft Testing Platform` extensions related to the hosting capability.
+This article lists and explains all Microsoft.Testing.Platform extensions related to the hosting capability.
 
 ## Hot reload
 
@@ -20,7 +20,7 @@ Hot reload lets you modify your app's managed source code while the application
 This extension is shipped as part of the [Microsoft.Testing.Extensions.HotReload](https://nuget.org/packages/Microsoft.Testing.Extensions.HotReload) package.
 
 > [!NOTE]
-> The package is shipped with the restrictive Microsoft Testing Platform Tools license.
+> The package is shipped with the restrictive Microsoft.Testing.Platform Tools license.
 > The full license is available at <https://www.nuget.org/packages/Microsoft.Testing.Extensions.HotReload/1.0.0/License>.
 
 You can easily enable hot reload support by setting the `TESTINGPLATFORM_HOTRELOAD_ENABLED` environment variable to `"1"`.

docs/core/testing/microsoft-testing-platform-extensions-output.md

@@ -8,7 +8,7 @@ ms.date: 08/26/2024
 
 # Output extensions
 
-This article list and explains all **Microsoft Testing Platform** extensions related to the terminal output.
+This article lists and explains all Microsoft.Testing.Platform extensions related to the terminal output.
 
 ## Terminal test reporter
 

docs/core/testing/microsoft-testing-platform-extensions-policy.md

@@ -8,7 +8,7 @@ ms.date: 04/10/2024
 
 # Policy extensions
 
-This article list and explains all `Microsoft Testing Platform` extensions related to the policy capability.
+This article lists and explains all Microsoft.Testing.Platform extensions related to the policy capability.
 
 ## Retry
 
@@ -19,7 +19,7 @@ This extension is intended for integration tests where the test depends heavily
 This extension is shipped as part of [Microsoft.Testing.Extensions.Retry](https://nuget.org/packages/Microsoft.Testing.Extensions.Retry) package.
 
 > [!NOTE]
-> The package is shipped with the restrictive Microsoft Testing Platform Tools license.
+> The package is shipped with the restrictive Microsoft.Testing.Platform Tools license.
 > The full license is available at <https://www.nuget.org/packages/Microsoft.Testing.Extensions.Retry/1.0.0/License>.
 
 The available options are as follows:

docs/core/testing/microsoft-testing-platform-extensions-test-reports.md

@@ -8,7 +8,7 @@ ms.date: 04/10/2024
 
 # Test reports extensions
 
-This article list and explains all `Microsoft Testing Platform` extensions related to the test report capability.
+This article lists and explains all Microsoft.Testing.Platform extensions related to the test report capability.
 
 A test report is a file that contains information about the execution and outcome of the tests.
 

docs/core/testing/microsoft-testing-platform-integration-dotnet-test.md

@@ -1,119 +1,28 @@
 ---
-title: Use Microsoft.Testing.Platform with `dotnet test`
+title: Use Microsoft.Testing.Platform with VSTest mode of `dotnet test`
 description: Learn how to run Microsoft.Testing.Platform tests through dotnet test.
 author: nohwnd
 ms.author: jajares
-ms.date: 12/20/2023
+ms.date: 03/26/2025
 ---
 
-# Use Microsoft.Testing.Platform with `dotnet test`
+# Use Microsoft.Testing.Platform with VSTest mode of `dotnet test`
 
-This article describes how to use `dotnet test` to run tests when using `Microsoft.Testing.Platform`, and the various options that are available to configure the MSBuild output produced when running tests through Microsoft.Testing.Platform.
+This article describes `dotnet test` integration for Microsoft.Testing.Platform that is provided by Microsoft.Testing.Platform.MSBuild when running with VSTest mode of `dotnet test`.
 
-This article shows how to use `dotnet test` to run all tests in a solution (_*.sln_) that uses `Microsoft.Testing.Platform`.
+Before reading this article, it's advised to read [Testing with dotnet test](unit-testing-with-dotnet-test.md) first.
 
-## `dotnet test` integration
+By default, `dotnet test` is using VSTest behavior to run tests. To enable support for `Microsoft.Testing.Platform` in `dotnet test`, there are two options:
 
-The [dotnet test](../tools/dotnet-test.md) command is a way to run tests from solutions, projects, or already built assemblies. [Microsoft.Testing.Platform](microsoft-testing-platform-intro.md) hooks up into this infrastructure to provide a unified way to run tests, especially when migrating from VSTest to `Microsoft.Testing.Platform`.
+1. Use `dotnet test` in VSTest mode, and specify `<TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport>` MSBuild property in your project file.
+2. Use `dotnet test` in MTP mode, and enjoy more native support of MTP in `dotnet test`. This is only supported starting with .NET 10 SDK.
 
-### `dotnet test` integration - VSTest mode
-
-`Microsoft.Testing.Platform` provides a [compatibility layer (VSTest Bridge)](./microsoft-testing-platform-extensions-vstest-bridge.md) to work with `dotnet test` seamlessly.
-
-Tests can be run by running:
-
-```dotnetcli
-dotnet test
-```
-
-This layer runs test through VSTest and integrates with it on VSTest Test Framework Adapter level.
-
-### `dotnet test` - Microsoft.Testing.Platform mode
-
-By default, `dotnet test` is using VSTest behavior to run tests. You can enable support for `Microsoft.Testing.Platform` in `dotnet test` by specifying the `<TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport>` setting in your project file.
-
-```xml
-<Project Sdk="Microsoft.NET.Sdk">
-
-  <PropertyGroup>
-    <TargetFramework>net8.0</TargetFramework>
-    <ImplicitUsings>enable</ImplicitUsings>
-    <Nullable>enable</Nullable>
-
-    <IsPackable>false</IsPackable>
-
-    <OutputType>Exe</OutputType>
-    <EnableMSTestRunner>true</EnableMSTestRunner>
-
-    <!-- Add this to your project file. -->
-    <TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport>
-
-  </PropertyGroup>
-
-  <!-- ... -->
-
-</Project>
-```
-
-> [!NOTE]
-> It's highly recommended that you set the `TestingPlatformDotnetTestSupport` property in `Directory.Build.props`. That way, you don't have to add it to every test project file, and you don't risk introducing a new project that doesn't set this property and end up with a solution where some projects are VSTest while others are Microsoft.Testing.Platform, which may not work correctly and is unsupported scenario.
+Both of these options are explained in details in the [Testing with dotnet test](unit-testing-with-dotnet-test.md) article.
 
 > [!IMPORTANT]
-> Despite `TestingPlatformDotnetTestSupport` being set to `true`, most of the command line options defined in [dotnet test](../tools/dotnet-test.md) remain VSTest oriented and don't impact `Microsoft.Testing.Platform` based tests. To supply arguments to `Microsoft.Testing.Platform`, you need to use one of the methods described in [Microsoft.Testing.Platform command line arguments with dotnet test](#microsofttestingplatform-command-line-arguments-with-dotnet-test).
-
-The list below described all `dotnet test` command line options that are supported by `Microsoft.Testing.Platform`:
-
-- `-a|--arch <ARCHITECTURE>`
-- `--artifacts-path <ARTIFACTS_DIR>`
-- `-c|--configuration <CONFIGURATION>`
-- `-f|--framework <FRAMEWORK>`
-- `-e|--environment <NAME="VALUE">`
-- `--interactive`
-- `--no-build`
-- `--nologo`
-- `--no-restore`
-- `-o|--output <OUTPUT_DIRECTORY>`
-- `--os <OS>`
-- `-r|--runtime <RUNTIME_IDENTIFIER>`
-- `-v|--verbosity <LEVEL>`
-
-These arguments are supported because they are linked to the build step and are independent of the testing platform used.
-
-### `Microsoft.Testing.Platform` command line arguments with `dotnet test`
-
-You can supply arguments that are used to call the testing application in one of the following ways:
-
-- Beginning with `Microsoft.Testing.Platform` version 1.4 (included with MSTest version 3.6), you can add options after the double dash `--` on the command line:
-
-    ```dotnetcli
-    dotnet test -- --minimum-expected-tests 10
-    ```
-
-- By using the `TestingPlatformCommandLineArguments` MSBuild property on the command line:
-
-    ```dotnetcli
-    dotnet test -p:TestingPlatformCommandLineArguments="--minimum-expected-tests 10"
-    ```
-
-  Or in the project file:
-
-  ```xml
-  <PropertyGroup>
-    ...
-    <TestingPlatformCommandLineArguments>--minimum-expected-tests 10</TestingPlatformCommandLineArguments>
-  </PropertyGroup>
-  ```
-
-## Additional MSBuild options
-
-The MSBuild integration provides options that can be specified in the project file or through global properties on the command line, such as `-p:TestingPlatformShowTestsFailure=true`.
-
-These are the available options:
-
-- [Show failure per test](#show-failure-per-test)
-- [Show complete platform output](#show-complete-platform-output)
+> The remaining of this article is specific to the first option.
 
-### Show failure per test
+## Show failure per test
 
 By default, test failures are summarized into a _.log_ file, and a single failure per test project is reported to MSBuild.
 
@@ -152,7 +61,7 @@ Or in project file:
 </Project>
 ```
 
-### Show complete platform output
+## Show complete platform output
 
 By default, all console output that the underlying test executable writes is captured and hidden from the user. This includes the banner, version information, and formatted test information.