Follow-up on test platforms docs refactoring#51978
Open
Evangelink wants to merge 8 commits intomainfrom
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Follow-up documentation refinements to the .NET testing platform content, focusing on clarifying platform selection guidance and updating Microsoft.Testing.Platform (MTP) reference pages after the earlier refactor in #51854.
Changes:
- Update platform selection guidance (including new scenarios and updated
dotnet testnotes). - Refresh MTP docs (retry API call shape, TRX report details, exit code list, and various wording/title improvements).
- Adjust MTP architecture docs to reflect updated guidance and API surface descriptions.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/core/testing/test-platforms-overview.md | Updates guidance on choosing VSTest vs MTP, including new scenarios and revised mixing/dotnet-test messaging. |
| docs/core/testing/microsoft-testing-platform-troubleshooting.md | Updates the documented exit code list (marks exit code 5 as no longer produced). |
| docs/core/testing/microsoft-testing-platform-test-reports.md | Adds guidance about manual TRX provider registration order and updates the default TRX filename format description. |
| docs/core/testing/microsoft-testing-platform-retry.md | Updates manual registration example to use builder.AddRetryProvider(). |
| docs/core/testing/microsoft-testing-platform-features.md | Refines scenario navigation text (telemetry phrasing). |
| docs/core/testing/microsoft-testing-platform-fakes.md | Updates article title metadata for clarity. |
| docs/core/testing/microsoft-testing-platform-extensions-vstest-bridge.md | Rewords the intro to better position the bridge extension’s purpose. |
| docs/core/testing/microsoft-testing-platform-architecture-test-framework.md | Updates architecture guidance and type descriptions for ITestFramework and related APIs. |
| docs/core/testing/microsoft-testing-platform-architecture-extensions.md | Clarifies the page title and section naming for extension points. |
Comments suppressed due to low confidence (1)
docs/core/testing/test-platforms-overview.md:50
- The
dotnet testrow for MTP omits the key pre-.NET 10 behavior (VSTest mode viaTestingPlatformDotnetTestSupportplus the extra--separator), which is still documented elsewhere (for example,migrating-vstest-microsoft-testing-platform.mdandunit-testing-with-dotnet-test.md). Consider adding a brief “In .NET 9 SDK and earlier…” note here (or explicitly defer to the linkedunit-testing-with-dotnet-test.md) to avoid misleading readers on older SDKs.
| `dotnet test` behavior | Default VSTest mode. VSTest arguments and behavior apply. | Native MTP mode is available in .NET 10 SDK and later. |
docs/core/testing/microsoft-testing-platform-troubleshooting.md
Outdated
Show resolved
Hide resolved
docs/core/testing/microsoft-testing-platform-extensions-vstest-bridge.md
Outdated
Show resolved
Hide resolved
docs/core/testing/microsoft-testing-platform-architecture-test-framework.md
Show resolved
Hide resolved
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Evangelink
commented
Mar 3, 2026
docs/core/testing/microsoft-testing-platform-extensions-vstest-bridge.md
Outdated
Show resolved
Hide resolved
Youssef1313
reviewed
Mar 4, 2026
docs/core/testing/microsoft-testing-platform-troubleshooting.md
Outdated
Show resolved
Hide resolved
Youssef1313
reviewed
Mar 4, 2026
Youssef1313
reviewed
Mar 4, 2026
Co-authored-by: Youssef Victor <youssefvictor00@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up from #51854
Internal previews