From bdd20e94874deee5ccaaac3637b5415d9bc3bd85 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Amaury=20Lev=C3=A9?= Date: Fri, 3 Jul 2026 13:27:30 +0200 Subject: [PATCH 1/2] Reorganize MTP features by functionality; document GitHub Actions report Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- .../microsoft-testing-platform-features.md | 38 ++++++++++--------- 1 file changed, 20 insertions(+), 18 deletions(-) diff --git a/docs/core/testing/microsoft-testing-platform-features.md b/docs/core/testing/microsoft-testing-platform-features.md index 18c9b8019cff9..147b95f48dcaa 100644 --- a/docs/core/testing/microsoft-testing-platform-features.md +++ b/docs/core/testing/microsoft-testing-platform-features.md @@ -3,7 +3,7 @@ title: Microsoft.Testing.Platform features description: Learn about the various Microsoft.Testing.Platform features, both built-in and available as extensions. author: nohwnd ms.author: jajares -ms.date: 02/25/2026 +ms.date: 07/03/2026 ai-usage: ai-assisted --- @@ -17,6 +17,8 @@ If you opt out of the auto-generated entry point by setting ` [!NOTE] -> The Microsoft.Extensions.Logging bridge was introduced in MTP 2.3.0. - -The [Microsoft.Testing.Extensions.Logging](https://www.nuget.org/packages/Microsoft.Testing.Extensions.Logging) package bridges Microsoft.Testing.Platform diagnostics to , so platform and extension logs flow through the same `Microsoft.Extensions.Logging` pipeline your application already uses. +**[Video recorder](https://www.nuget.org/packages/Microsoft.Testing.Extensions.VideoRecorder)** (experimental, introduced in MTP 2.3.0) -Manual registration: +Record the screen during a test run. It requires `ffmpeg` to be available on the machine and is enabled with the `--capture-video` option. Register it manually with `builder.AddVideoRecorderProvider()`. -```csharp -var builder = await TestApplication.CreateBuilderAsync(args); -builder.AddMicrosoftExtensionsLogging(logging => logging.AddConsole()); -``` +**[Packaged app deployment](https://www.nuget.org/packages/Microsoft.Testing.Extensions.PackagedApp)** (experimental, introduced in MTP 2.3.0) -## Experimental extensions +A reference extension that uses the experimental `ITestHostLauncher` extension point to deploy and launch a packaged-app test host. Register it manually with `builder.AddPackagedAppDeployment()`. -The following extensions are experimental. Their APIs are annotated with the `TPEXP` diagnostic and might change in a future release; using them requires acknowledging the experimental diagnostic. For more information, see [Microsoft.Testing.Platform diagnostics](https://aka.ms/testingplatform/diagnostics). +## Microsoft.Extensions integration -**[Video recorder](https://www.nuget.org/packages/Microsoft.Testing.Extensions.VideoRecorder)** (experimental, introduced in MTP 2.3.0) +These extensions bridge Microsoft.Testing.Platform to the `Microsoft.Extensions.*` libraries your application already uses. -Records the screen during a test run. It requires `ffmpeg` to be available on the machine and is enabled with the `--capture-video` option. Register it manually with `builder.AddVideoRecorderProvider()`. +**[Logging bridge](https://www.nuget.org/packages/Microsoft.Testing.Extensions.Logging)** (experimental, introduced in MTP 2.3.0) -**[Packaged app deployment](https://www.nuget.org/packages/Microsoft.Testing.Extensions.PackagedApp)** (experimental, introduced in MTP 2.3.0) +The Microsoft.Testing.Extensions.Logging package bridges Microsoft.Testing.Platform diagnostics to , so platform and extension logs flow through the same `Microsoft.Extensions.Logging` pipeline your application already uses. Register it manually with the following call: -A reference extension that uses the experimental `ITestHostLauncher` extension point to deploy and launch a packaged-app test host. Register it manually with `builder.AddPackagedAppDeployment()`. +```csharp +var builder = await TestApplication.CreateBuilderAsync(args); +builder.AddMicrosoftExtensionsLogging(logging => logging.AddConsole()); +``` From 1aa6fca7f7797f52556a0d84db74646c8010d6d3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Amaury=20Lev=C3=A9?= Date: Fri, 3 Jul 2026 13:48:21 +0200 Subject: [PATCH 2/2] Address review: Oxford comma, Markdown casing, clarify slow-test-threshold Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- docs/core/testing/microsoft-testing-platform-features.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/core/testing/microsoft-testing-platform-features.md b/docs/core/testing/microsoft-testing-platform-features.md index 147b95f48dcaa..93ae4a36e32c4 100644 --- a/docs/core/testing/microsoft-testing-platform-features.md +++ b/docs/core/testing/microsoft-testing-platform-features.md @@ -31,7 +31,7 @@ Use the following path based on your goal: - Need to customize terminal output: [Terminal output](./microsoft-testing-platform-terminal-output.md) (built-in) - Need TRX or Azure DevOps reports: [Test reports](./microsoft-testing-platform-test-reports.md) (extension) -- Need GitHub Actions-native output (log groups, annotations, job summary): [GitHub Actions report](https://www.nuget.org/packages/Microsoft.Testing.Extensions.GitHubActionsReport) (extension, experimental) +- Need GitHub Actions-native output (log groups, annotations, and job summary): [GitHub Actions report](https://www.nuget.org/packages/Microsoft.Testing.Extensions.GitHubActionsReport) (extension, experimental) - Need coverage data: [Code coverage](./microsoft-testing-platform-code-coverage.md) (extension) - Need crash or hang diagnostics: [Crash and hang dumps](./microsoft-testing-platform-crash-hang-dumps.md) (extension) - Need to retry failed tests: [Retry](./microsoft-testing-platform-retry.md#retry) (extension) @@ -58,7 +58,7 @@ Generate test report files (TRX, Azure DevOps). **[GitHub Actions report](https://www.nuget.org/packages/Microsoft.Testing.Extensions.GitHubActionsReport)** (experimental, introduced in MTP 2.3.0) -Emit GitHub Actions-native workflow commands so test runs produce a first-class experience: per-assembly log groups, failure annotations (surfaced in the workflow **Annotations** tab and, when the source location resolves, on the pull request's **Files changed** diff), a markdown job summary appended to `GITHUB_STEP_SUMMARY`, and slow-test notices. The extension activates automatically when the `GITHUB_ACTIONS` environment variable is `true`, or elsewhere with the `--report-gh` switch. Each feature is individually toggleable through the `--report-gh-groups`, `--report-gh-annotations`, `--report-gh-step-summary`, `--report-gh-slow-test-notices`, and `--report-gh-slow-test-threshold` options. Register it manually with `builder.AddGitHubActionsProvider()`. +Emit GitHub Actions-native workflow commands so test runs produce a first-class experience: per-assembly log groups, failure annotations (surfaced in the workflow **Annotations** tab and, when the source location resolves, on the pull request's **Files changed** diff), a Markdown job summary appended to `GITHUB_STEP_SUMMARY`, and slow-test notices. The extension activates automatically when the `GITHUB_ACTIONS` environment variable is `true`, or elsewhere with the `--report-gh` switch. Each feature can be turned on or off individually with the `--report-gh-groups`, `--report-gh-annotations`, `--report-gh-step-summary`, and `--report-gh-slow-test-notices` options, and the slow-test threshold is set with `--report-gh-slow-test-threshold`. Register it manually with `builder.AddGitHubActionsProvider()`. **[Code coverage](./microsoft-testing-platform-code-coverage.md)**