Remove redundant MTP VSTest integration page

.openpublishing.redirection.core.json

@@ -1583,6 +1583,10 @@
       "source_path_from_root": "/docs/core/run-time-config/threading.md",
       "redirect_url": "/dotnet/core/runtime-config/threading"
     },
+    {
+      "source_path_from_root": "/docs/core/testing/microsoft-testing-platform-integration-dotnet-test.md",
+      "redirect_url": "/dotnet/core/testing/unit-testing-with-dotnet-test"
+    },
     {
       "source_path_from_root": "/docs/core/testing/using-mstest-on-windows.md",
       "redirect_url": "/dotnet/core/testing/unit-testing-csharp-with-mstest",
@@ -1665,7 +1669,7 @@
     },
     {
       "source_path_from_root": "/docs/core/testing/unit-testing-mstest-runner-integrations.md",
-      "redirect_url": "/dotnet/core/testing/microsoft-testing-platform-integration-dotnet-test",
+      "redirect_url": "/dotnet/core/testing/unit-testing-with-dotnet-test",
       "redirect_document_id": true
     },
     {
@@ -2006,7 +2010,7 @@
     },
     {
       "source_path_from_root": "/docs/core/testing/unit-testing-platform-integration-dotnet-test.md",
-      "redirect_url": "/dotnet/core/testing/microsoft-testing-platform-integration-dotnet-test"
+      "redirect_url": "/dotnet/core/testing/unit-testing-with-dotnet-test"
     },
     {
       "source_path_from_root": "/docs/core/testing/unit-testing-platform-intro.md",

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

@@ -1600,7 +1600,7 @@ The `GenerateTestingPlatformConfigurationFile` property is only available when [
 
 The `TestingPlatformCaptureOutput` property controls whether all console output that a test executable writes is captured and hidden from the user when you use `dotnet test` to run `Microsoft.Testing.Platform` tests. By default, the console output is hidden. This output includes the banner, version information, and formatted test information. Set this property to `false` to show this information together with MSBuild output.
 
-For more information, see [Show complete platform output](../testing/microsoft-testing-platform-integration-dotnet-test.md#show-complete-platform-output).
+For more information, see [Show complete platform output](../testing/unit-testing-with-dotnet-test.md#show-complete-platform-output).
 
 ### TestingPlatformCommandLineArguments
 

docs/core/testing/unit-testing-mstest-running-tests.md

@@ -53,7 +53,7 @@ Consider the following example project file:
 
     <!--
       Displays error on console in addition to the log file. Note that this feature comes with a performance impact.
-      For more information, visit https://learn.microsoft.com/dotnet/core/testing/microsoft-testing-platform-integration-dotnet-test#show-failure-per-test
+      For more information, visit https://learn.microsoft.com/dotnet/core/testing/unit-testing-with-dotnet-test#show-failure-per-test
       -->
     <TestingPlatformShowTestsFailure>true</TestingPlatformShowTestsFailure>
 

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

@@ -11,7 +11,7 @@ ms.date: 02/13/2024
 This article covers advanced configuration options for MSTest.Sdk. For basic setup and getting started, see [Get started with MSTest](./unit-testing-mstest-getting-started.md).
 
 > [!IMPORTANT]
-> By default, MSTest.Sdk uses the [MSTest runner with Microsoft.Testing.Platform](./unit-testing-mstest-running-tests.md), including with [dotnet test](./microsoft-testing-platform-integration-dotnet-test.md). This requires modifying your CI and local CLI calls, and also impacts the available entries of the _.runsettings_. You can keep the old integrations and tools by [switching to VSTest](#select-the-runner).
+> By default, MSTest.Sdk uses the [MSTest runner with Microsoft.Testing.Platform](./unit-testing-mstest-running-tests.md), including with [dotnet test](./unit-testing-with-dotnet-test.md). This requires modifying your CI and local CLI calls, and also impacts the available entries of the _.runsettings_. You can keep the old integrations and tools by [switching to VSTest](#select-the-runner).
 >
 > MSTest.Sdk sets `EnableMSTestRunner` and `TestingPlatformDotnetTestSupport` to true by default. For more information about dotnet test and its different modes, see [Testing with dotnet test](./unit-testing-with-dotnet-test.md).
 

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

@@ -34,7 +34,7 @@ Consider the following example project file:
 
     <!--
       Displays error on console in addition to the log file. Note that this feature comes with a performance impact.
-      For more information, visit https://learn.microsoft.com/dotnet/core/testing/microsoft-testing-platform-integration-dotnet-test#show-failure-per-test
+      For more information, visit https://learn.microsoft.com/dotnet/core/testing/unit-testing-with-dotnet-test#show-failure-per-test
       -->
     <TestingPlatformShowTestsFailure>true</TestingPlatformShowTestsFailure>
 

docs/core/testing/unit-testing-with-dotnet-test.md

@@ -65,7 +65,31 @@ The following list outlines the command-line options of `dotnet test` command in
 > </PropertyGroup>
 > ```
 
-For more information specific to running MTP projects in VSTest mode of `dotnet test`, see [Use Microsoft.Testing.Platform with VSTest mode of `dotnet test`](./microsoft-testing-platform-integration-dotnet-test.md).
+#### 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.
+
+To show errors per failed test, specify `-p:TestingPlatformShowTestsFailure=true` on the command line, or add the `<TestingPlatformShowTestsFailure>true</TestingPlatformShowTestsFailure>` property to your project file.
+
+On command line:
+
+```dotnetcli
+dotnet test -p:TestingPlatformShowTestsFailure=true
+```
+
+#### 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.
+
+To show this information together with MSBuild output, use `<TestingPlatformCaptureOutput>false</TestingPlatformCaptureOutput>`.
+
+This option doesn't impact how the testing framework captures user output written by `Console.WriteLine` or other similar ways to write to the console.
+
+On command line:
+
+```dotnetcli
+dotnet test -p:TestingPlatformCaptureOutput=false
+```
 
 #### Advanced technical details