Split TerminalTestReporter.Summary.cs into focused partial files

[Amaury Levé (Evangelink)]

Fixes#10367

TerminalTestReporter.Summary.cs had grown to 715 lines and mixed several unrelated concerns. This splits it along the existing logical boundaries, following the established TerminalTestReporter.<Concern>.cs convention.

File	Contents	Lines
TerminalTestReporter.Summary.cs(trimmed)	AppendTestRunSummary, AppendRetrySummaryLines	248
TerminalTestReporter.Coverage.cs(new)	AppendCoverageSummary (internal + private), FormatThresholdPercentages, GetCoverage*Label helpers	204
TerminalTestReporter.TestDiscovery.cs(new)	TestDiscovered (both overloads), AppendTestDiscoverySummary	134
TerminalTestReporter.FlakyTests.cs(new)	AppendFlakyTests, AppendFlakyTestLine	83
TerminalTestReporter.SlowestTests.cs(new)	AppendSlowestTests, AppendSlowestTestLine	79

Two deviations from the issue text, both deliberate:

• Five files, not three. The issue required every file be under 350 lines, but its own 3-way split leaves the trimmed Summary.cs at ~394 lines. Breaking out the flaky and slowest sections is what actually satisfies the stated criterion, and SlowestTests.cs at 79 lines is in line with the existing ErroredAssemblies.cs at 75.
• TestDiscovery.cs, not Discovery.cs, so it pairs with the existing TerminalTestReporter.TestCompletion.cs — the mirror concern.

AppendRetrySummaryLines stays in Summary.cs: it emits the flaky: / retried: counter lines inline between the skipped count and the duration, so it belongs with the rest of the counter block rather than with the separate "Flaky tests" listing.

Also adds a <remarks> map of the partials to the type doc on TerminalTestReporter.cs, following the precedent in TrxResultStreamingStore.cs. At 13 partials the type had no signpost for where anything lives.

Not a behavior change

No member body was modified. Verified mechanically rather than by eye: the 606 non-empty class-body lines of the original file and of the five files replacing it are an identical multiset with zero diffs, and a per-member brace-depth chunker matches all 17 members byte-for-byte. Two private helpers changed position relative to the whole file, each moving adjacent to its sole caller — AppendSlowestTestLine (previously sitting after AppendFlakyTestLine) and AppendRetrySummaryLines. The only other non-move change is narrowing each file's using set; note that the issue's guideline #5 ("no new using directives needed, all files share the same using set as today") is wrong — copying all three usings everywhere would trip IDE0005, which is warning in .editorconfig with EnforceCodeStyleInBuild=true.

Note for downstream: dotnet/sdk

This reporter source is hard-forked into dotnet/sdk, whose eng/vendored-files.json tracks each partial individually (I checked — it lists TerminalTestReporter.cs, .ErroredAssemblies.cs, .Formatting.cs, .Handshake.cs, .Lifecycle.cs, .Messaging.cs, .Summary.cs, .TestCompletion.cs … each with "scope": "reporter partial").

TerminalReporterContract.props globs *.cs, so nothing needed to change on our side. But the four new paths are absent from the SDK manifest, so until it is updated, edits to the coverage / discovery / flaky / slowest code would be invisible to the SDK's drift workflow. The shrinking of Summary.cs will fire that workflow, so it should get noticed — tracked in #10390 regardless.

Validation

• Microsoft.Testing.Platform builds for net8.0 / net9.0 / netstandard2.0 — 0 warnings, which is what proves the using sets are exactly minimal.
• Microsoft.Testing.Platform.UnitTests — passing on net8.0, net9.0, net462.
• Microsoft.Testing.Platform.TerminalReporterContract.UnitTests — passing on net8.0 and net9.0, confirming the files still compile as a standalone shared-source consumer with no platform reference.

[Copilot]

Pull request overview

Splits the oversized terminal reporter summary into focused partial-class files without changing behavior.

Changes:

• Separates coverage and discovery reporting.
• Extracts flaky/retry and slowest-test rendering.
• Keeps all files below 350 lines.

Show a summary per file

File	Description
TerminalTestReporter.Summary.cs	Retains run-summary orchestration.
TerminalTestReporter.Coverage.cs	Contains coverage summary rendering.
TerminalTestReporter.Discovery.cs	Contains discovery tracking and summaries.
TerminalTestReporter.FlakyTests.cs	Contains retry and flaky-test output.
TerminalTestReporter.SlowestTests.cs	Contains slowest-test output.

Review details

• Files reviewed: 5/5 changed files
• Comments generated: 0
• Review effort level: Balanced

[github-actions]

Note

🤖 Automated review by GitHub Copilot. Generated by the Expert Code Review workflow. To request a follow-up action, reply by tagging @copilot directly.

Expert Review Summary

Verdict: No issues found ✅

This is a pure code-move refactoring — methods were relocated from TerminalTestReporter.Summary.cs into four new partial class files (Coverage, Discovery, FlakyTests, SlowestTests) with no behavioral changes.

Dimension	Result
Threading & Concurrency	LGTM — no new shared state or synchronization changes
Public API & Binary Compatibility	LGTM — all moved members are internal or private; no public API surface change
Performance & Allocations	LGTM — identical code paths
Cross-TFM Compatibility	LGTM — no new conditional compilation or TFM-specific code
Build Infrastructure	LGTM — *.cs glob picks up new files automatically
Scope & PR Discipline	LGTM — clean separation along logical boundaries, verified line-identical
Localization & Resources	LGTM — using sets correctly narrowed per file
Code Structure	LGTM — follows established TerminalTestReporter.<x>.cs convention

All new files correctly declare [UnsupportedOSPlatform("browser")] internal sealed partial class TerminalTestReporter and include only the using directives they actually need. No issues identified across any applicable review dimension.

[Copilot]

Review details

Suppressed comments (1)

src/Platform/Microsoft.Testing.Platform/OutputDevice/Terminal/TerminalTestReporter.cs:18

• The file inventory no longer matches the PR description: the implementation uses TerminalTestReporter.TestDiscovery.cs (not Discovery.cs), and AppendRetrySummaryLines remains in Summary.cs, making the actual Summary/FlakyTests sizes 248/83 rather than the documented 222/109. Since the downstream vendoring note depends on exact paths, please update the PR table and split rationale to reflect the committed layout, or move/rename the files to match it.

/// <c>TestDiscovery</c> (per-test execution and discovery output), <c>Summary</c> (the post-run verdict and counts),
/// <c>FlakyTests</c> and <c>SlowestTests</c> (the optional summary sections), <c>Coverage</c> (code-coverage and

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Copilot]

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Amaury Levé (Evangelink)]

Fixes#10367

TerminalTestReporter.Summary.cs had grown to 715 lines and mixed several unrelated concerns. This splits it along the existing logical boundaries, following the established TerminalTestReporter.<Concern>.cs convention.

File	Contents	Lines
TerminalTestReporter.Summary.cs(trimmed)	AppendTestRunSummary, AppendRetrySummaryLines	248
TerminalTestReporter.Coverage.cs(new)	AppendCoverageSummary (internal + private), FormatThresholdPercentages, GetCoverage*Label helpers	204
TerminalTestReporter.TestDiscovery.cs(new)	TestDiscovered (both overloads), AppendTestDiscoverySummary	134
TerminalTestReporter.FlakyTests.cs(new)	AppendFlakyTests, AppendFlakyTestLine	83
TerminalTestReporter.SlowestTests.cs(new)	AppendSlowestTests, AppendSlowestTestLine	79

Two deviations from the issue text, both deliberate:

• Five files, not three. The issue required every file be under 350 lines, but its own 3-way split leaves the trimmed Summary.cs at ~394 lines. Breaking out the flaky and slowest sections is what actually satisfies the stated criterion, and SlowestTests.cs at 79 lines is in line with the existing ErroredAssemblies.cs at 75.
• TestDiscovery.cs, not Discovery.cs, so it pairs with the existing TerminalTestReporter.TestCompletion.cs — the mirror concern.

AppendRetrySummaryLines stays in Summary.cs: it emits the flaky: / retried: counter lines inline between the skipped count and the duration, so it belongs with the rest of the counter block rather than with the separate "Flaky tests" listing.

Also adds a <remarks> map of the partials to the type doc on TerminalTestReporter.cs, following the precedent in TrxResultStreamingStore.cs. At 13 partials the type had no signpost for where anything lives.

Not a behavior change

No member body was modified. Verified mechanically rather than by eye: the 606 non-empty class-body lines of the original file and of the five files replacing it are an identical multiset with zero diffs, and a per-member brace-depth chunker matches all 17 members byte-for-byte. Two private helpers changed position relative to the whole file, each moving adjacent to its sole caller — AppendSlowestTestLine (previously sitting after AppendFlakyTestLine) and AppendRetrySummaryLines. The only other non-move change is narrowing each file's using set; note that the issue's guideline #5 ("no new using directives needed, all files share the same using set as today") is wrong — copying all three usings everywhere would trip IDE0005, which is warning in .editorconfig with EnforceCodeStyleInBuild=true.

Note for downstream: dotnet/sdk

This reporter source is hard-forked into dotnet/sdk, whose eng/vendored-files.json tracks each partial individually (I checked — it lists TerminalTestReporter.cs, .ErroredAssemblies.cs, .Formatting.cs, .Handshake.cs, .Lifecycle.cs, .Messaging.cs, .Summary.cs, .TestCompletion.cs … each with "scope": "reporter partial").

TerminalReporterContract.props globs *.cs, so nothing needed to change on our side. But the four new paths are absent from the SDK manifest, so until it is updated, edits to the coverage / discovery / flaky / slowest code would be invisible to the SDK's drift workflow. The shrinking of Summary.cs will fire that workflow, so it should get noticed — tracked in #10390 regardless.

Validation

• Microsoft.Testing.Platform builds for net8.0 / net9.0 / netstandard2.0 — 0 warnings, which is what proves the using sets are exactly minimal.
• Microsoft.Testing.Platform.UnitTests — passing on net8.0, net9.0, net462.
• Microsoft.Testing.Platform.TerminalReporterContract.UnitTests — passing on net8.0 and net9.0, confirming the files still compile as a standalone shared-source consumer with no platform reference.

[Copilot]

Pull request overview

Splits the oversized terminal reporter summary into focused partial-class files without changing behavior.

Changes:

• Separates coverage and discovery reporting.
• Extracts flaky/retry and slowest-test rendering.
• Keeps all files below 350 lines.

Show a summary per file

File	Description
TerminalTestReporter.Summary.cs	Retains run-summary orchestration.
TerminalTestReporter.Coverage.cs	Contains coverage summary rendering.
TerminalTestReporter.Discovery.cs	Contains discovery tracking and summaries.
TerminalTestReporter.FlakyTests.cs	Contains retry and flaky-test output.
TerminalTestReporter.SlowestTests.cs	Contains slowest-test output.

Review details

• Files reviewed: 5/5 changed files
• Comments generated: 0
• Review effort level: Balanced

[github-actions]

Note

🤖 Automated review by GitHub Copilot. Generated by the Expert Code Review workflow. To request a follow-up action, reply by tagging @copilot directly.

Expert Review Summary

Verdict: No issues found ✅

This is a pure code-move refactoring — methods were relocated from TerminalTestReporter.Summary.cs into four new partial class files (Coverage, Discovery, FlakyTests, SlowestTests) with no behavioral changes.

Dimension	Result
Threading & Concurrency	LGTM — no new shared state or synchronization changes
Public API & Binary Compatibility	LGTM — all moved members are internal or private; no public API surface change
Performance & Allocations	LGTM — identical code paths
Cross-TFM Compatibility	LGTM — no new conditional compilation or TFM-specific code
Build Infrastructure	LGTM — *.cs glob picks up new files automatically
Scope & PR Discipline	LGTM — clean separation along logical boundaries, verified line-identical
Localization & Resources	LGTM — using sets correctly narrowed per file
Code Structure	LGTM — follows established TerminalTestReporter.<x>.cs convention

All new files correctly declare [UnsupportedOSPlatform("browser")] internal sealed partial class TerminalTestReporter and include only the using directives they actually need. No issues identified across any applicable review dimension.

[Copilot]

Review details

Suppressed comments (1)

src/Platform/Microsoft.Testing.Platform/OutputDevice/Terminal/TerminalTestReporter.cs:18

• The file inventory no longer matches the PR description: the implementation uses TerminalTestReporter.TestDiscovery.cs (not Discovery.cs), and AppendRetrySummaryLines remains in Summary.cs, making the actual Summary/FlakyTests sizes 248/83 rather than the documented 222/109. Since the downstream vendoring note depends on exact paths, please update the PR table and split rationale to reflect the committed layout, or move/rename the files to match it.

/// <c>TestDiscovery</c> (per-test execution and discovery output), <c>Summary</c> (the post-run verdict and counts),
/// <c>FlakyTests</c> and <c>SlowestTests</c> (the optional summary sections), <c>Coverage</c> (code-coverage and

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Copilot]

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Amaury Levé (Evangelink)]

Fixes#10367

TerminalTestReporter.Summary.cs had grown to 715 lines and mixed several unrelated concerns. This splits it along the existing logical boundaries, following the established TerminalTestReporter.<Concern>.cs convention.

File	Contents	Lines
TerminalTestReporter.Summary.cs(trimmed)	AppendTestRunSummary, AppendRetrySummaryLines	248
TerminalTestReporter.Coverage.cs(new)	AppendCoverageSummary (internal + private), FormatThresholdPercentages, GetCoverage*Label helpers	204
TerminalTestReporter.TestDiscovery.cs(new)	TestDiscovered (both overloads), AppendTestDiscoverySummary	134
TerminalTestReporter.FlakyTests.cs(new)	AppendFlakyTests, AppendFlakyTestLine	83
TerminalTestReporter.SlowestTests.cs(new)	AppendSlowestTests, AppendSlowestTestLine	79

Two deviations from the issue text, both deliberate:

• Five files, not three. The issue required every file be under 350 lines, but its own 3-way split leaves the trimmed Summary.cs at ~394 lines. Breaking out the flaky and slowest sections is what actually satisfies the stated criterion, and SlowestTests.cs at 79 lines is in line with the existing ErroredAssemblies.cs at 75.
• TestDiscovery.cs, not Discovery.cs, so it pairs with the existing TerminalTestReporter.TestCompletion.cs — the mirror concern.

AppendRetrySummaryLines stays in Summary.cs: it emits the flaky: / retried: counter lines inline between the skipped count and the duration, so it belongs with the rest of the counter block rather than with the separate "Flaky tests" listing.

Also adds a <remarks> map of the partials to the type doc on TerminalTestReporter.cs, following the precedent in TrxResultStreamingStore.cs. At 13 partials the type had no signpost for where anything lives.

Not a behavior change

No member body was modified. Verified mechanically rather than by eye: the 606 non-empty class-body lines of the original file and of the five files replacing it are an identical multiset with zero diffs, and a per-member brace-depth chunker matches all 17 members byte-for-byte. Two private helpers changed position relative to the whole file, each moving adjacent to its sole caller — AppendSlowestTestLine (previously sitting after AppendFlakyTestLine) and AppendRetrySummaryLines. The only other non-move change is narrowing each file's using set; note that the issue's guideline #5 ("no new using directives needed, all files share the same using set as today") is wrong — copying all three usings everywhere would trip IDE0005, which is warning in .editorconfig with EnforceCodeStyleInBuild=true.

Note for downstream: dotnet/sdk

This reporter source is hard-forked into dotnet/sdk, whose eng/vendored-files.json tracks each partial individually (I checked — it lists TerminalTestReporter.cs, .ErroredAssemblies.cs, .Formatting.cs, .Handshake.cs, .Lifecycle.cs, .Messaging.cs, .Summary.cs, .TestCompletion.cs … each with "scope": "reporter partial").

TerminalReporterContract.props globs *.cs, so nothing needed to change on our side. But the four new paths are absent from the SDK manifest, so until it is updated, edits to the coverage / discovery / flaky / slowest code would be invisible to the SDK's drift workflow. The shrinking of Summary.cs will fire that workflow, so it should get noticed — tracked in #10390 regardless.

Validation

• Microsoft.Testing.Platform builds for net8.0 / net9.0 / netstandard2.0 — 0 warnings, which is what proves the using sets are exactly minimal.
• Microsoft.Testing.Platform.UnitTests — passing on net8.0, net9.0, net462.
• Microsoft.Testing.Platform.TerminalReporterContract.UnitTests — passing on net8.0 and net9.0, confirming the files still compile as a standalone shared-source consumer with no platform reference.

[Copilot]

Pull request overview

Splits the oversized terminal reporter summary into focused partial-class files without changing behavior.

Changes:

• Separates coverage and discovery reporting.
• Extracts flaky/retry and slowest-test rendering.
• Keeps all files below 350 lines.

Show a summary per file

File	Description
TerminalTestReporter.Summary.cs	Retains run-summary orchestration.
TerminalTestReporter.Coverage.cs	Contains coverage summary rendering.
TerminalTestReporter.Discovery.cs	Contains discovery tracking and summaries.
TerminalTestReporter.FlakyTests.cs	Contains retry and flaky-test output.
TerminalTestReporter.SlowestTests.cs	Contains slowest-test output.

Review details

• Files reviewed: 5/5 changed files
• Comments generated: 0
• Review effort level: Balanced

[github-actions]

Note

🤖 Automated review by GitHub Copilot. Generated by the Expert Code Review workflow. To request a follow-up action, reply by tagging @copilot directly.

Expert Review Summary

Verdict: No issues found ✅

This is a pure code-move refactoring — methods were relocated from TerminalTestReporter.Summary.cs into four new partial class files (Coverage, Discovery, FlakyTests, SlowestTests) with no behavioral changes.

Dimension	Result
Threading & Concurrency	LGTM — no new shared state or synchronization changes
Public API & Binary Compatibility	LGTM — all moved members are internal or private; no public API surface change
Performance & Allocations	LGTM — identical code paths
Cross-TFM Compatibility	LGTM — no new conditional compilation or TFM-specific code
Build Infrastructure	LGTM — *.cs glob picks up new files automatically
Scope & PR Discipline	LGTM — clean separation along logical boundaries, verified line-identical
Localization & Resources	LGTM — using sets correctly narrowed per file
Code Structure	LGTM — follows established TerminalTestReporter.<x>.cs convention

All new files correctly declare [UnsupportedOSPlatform("browser")] internal sealed partial class TerminalTestReporter and include only the using directives they actually need. No issues identified across any applicable review dimension.

[Copilot]

Review details

Suppressed comments (1)

src/Platform/Microsoft.Testing.Platform/OutputDevice/Terminal/TerminalTestReporter.cs:18

• The file inventory no longer matches the PR description: the implementation uses TerminalTestReporter.TestDiscovery.cs (not Discovery.cs), and AppendRetrySummaryLines remains in Summary.cs, making the actual Summary/FlakyTests sizes 248/83 rather than the documented 222/109. Since the downstream vendoring note depends on exact paths, please update the PR table and split rationale to reflect the committed layout, or move/rename the files to match it.

/// <c>TestDiscovery</c> (per-test execution and discovery output), <c>Summary</c> (the post-run verdict and counts),
/// <c>FlakyTests</c> and <c>SlowestTests</c> (the optional summary sections), <c>Coverage</c> (code-coverage and

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Copilot]

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Amaury Levé (Evangelink)]

Fixes#10367

TerminalTestReporter.Summary.cs had grown to 715 lines and mixed several unrelated concerns. This splits it along the existing logical boundaries, following the established TerminalTestReporter.<Concern>.cs convention.

File	Contents	Lines
TerminalTestReporter.Summary.cs(trimmed)	AppendTestRunSummary, AppendRetrySummaryLines	248
TerminalTestReporter.Coverage.cs(new)	AppendCoverageSummary (internal + private), FormatThresholdPercentages, GetCoverage*Label helpers	204
TerminalTestReporter.TestDiscovery.cs(new)	TestDiscovered (both overloads), AppendTestDiscoverySummary	134
TerminalTestReporter.FlakyTests.cs(new)	AppendFlakyTests, AppendFlakyTestLine	83
TerminalTestReporter.SlowestTests.cs(new)	AppendSlowestTests, AppendSlowestTestLine	79

Two deviations from the issue text, both deliberate:

• Five files, not three. The issue required every file be under 350 lines, but its own 3-way split leaves the trimmed Summary.cs at ~394 lines. Breaking out the flaky and slowest sections is what actually satisfies the stated criterion, and SlowestTests.cs at 79 lines is in line with the existing ErroredAssemblies.cs at 75.
• TestDiscovery.cs, not Discovery.cs, so it pairs with the existing TerminalTestReporter.TestCompletion.cs — the mirror concern.

AppendRetrySummaryLines stays in Summary.cs: it emits the flaky: / retried: counter lines inline between the skipped count and the duration, so it belongs with the rest of the counter block rather than with the separate "Flaky tests" listing.

Also adds a <remarks> map of the partials to the type doc on TerminalTestReporter.cs, following the precedent in TrxResultStreamingStore.cs. At 13 partials the type had no signpost for where anything lives.

Not a behavior change

No member body was modified. Verified mechanically rather than by eye: the 606 non-empty class-body lines of the original file and of the five files replacing it are an identical multiset with zero diffs, and a per-member brace-depth chunker matches all 17 members byte-for-byte. Two private helpers changed position relative to the whole file, each moving adjacent to its sole caller — AppendSlowestTestLine (previously sitting after AppendFlakyTestLine) and AppendRetrySummaryLines. The only other non-move change is narrowing each file's using set; note that the issue's guideline #5 ("no new using directives needed, all files share the same using set as today") is wrong — copying all three usings everywhere would trip IDE0005, which is warning in .editorconfig with EnforceCodeStyleInBuild=true.

Note for downstream: dotnet/sdk

This reporter source is hard-forked into dotnet/sdk, whose eng/vendored-files.json tracks each partial individually (I checked — it lists TerminalTestReporter.cs, .ErroredAssemblies.cs, .Formatting.cs, .Handshake.cs, .Lifecycle.cs, .Messaging.cs, .Summary.cs, .TestCompletion.cs … each with "scope": "reporter partial").

TerminalReporterContract.props globs *.cs, so nothing needed to change on our side. But the four new paths are absent from the SDK manifest, so until it is updated, edits to the coverage / discovery / flaky / slowest code would be invisible to the SDK's drift workflow. The shrinking of Summary.cs will fire that workflow, so it should get noticed — tracked in #10390 regardless.

Validation

• Microsoft.Testing.Platform builds for net8.0 / net9.0 / netstandard2.0 — 0 warnings, which is what proves the using sets are exactly minimal.
• Microsoft.Testing.Platform.UnitTests — passing on net8.0, net9.0, net462.
• Microsoft.Testing.Platform.TerminalReporterContract.UnitTests — passing on net8.0 and net9.0, confirming the files still compile as a standalone shared-source consumer with no platform reference.

[Copilot]

Pull request overview

Splits the oversized terminal reporter summary into focused partial-class files without changing behavior.

Changes:

• Separates coverage and discovery reporting.
• Extracts flaky/retry and slowest-test rendering.
• Keeps all files below 350 lines.

Show a summary per file

File	Description
TerminalTestReporter.Summary.cs	Retains run-summary orchestration.
TerminalTestReporter.Coverage.cs	Contains coverage summary rendering.
TerminalTestReporter.Discovery.cs	Contains discovery tracking and summaries.
TerminalTestReporter.FlakyTests.cs	Contains retry and flaky-test output.
TerminalTestReporter.SlowestTests.cs	Contains slowest-test output.

Review details

• Files reviewed: 5/5 changed files
• Comments generated: 0
• Review effort level: Balanced

[github-actions]

Note

🤖 Automated review by GitHub Copilot. Generated by the Expert Code Review workflow. To request a follow-up action, reply by tagging @copilot directly.

Expert Review Summary

Verdict: No issues found ✅

This is a pure code-move refactoring — methods were relocated from TerminalTestReporter.Summary.cs into four new partial class files (Coverage, Discovery, FlakyTests, SlowestTests) with no behavioral changes.

Dimension	Result
Threading & Concurrency	LGTM — no new shared state or synchronization changes
Public API & Binary Compatibility	LGTM — all moved members are internal or private; no public API surface change
Performance & Allocations	LGTM — identical code paths
Cross-TFM Compatibility	LGTM — no new conditional compilation or TFM-specific code
Build Infrastructure	LGTM — *.cs glob picks up new files automatically
Scope & PR Discipline	LGTM — clean separation along logical boundaries, verified line-identical
Localization & Resources	LGTM — using sets correctly narrowed per file
Code Structure	LGTM — follows established TerminalTestReporter.<x>.cs convention

All new files correctly declare [UnsupportedOSPlatform("browser")] internal sealed partial class TerminalTestReporter and include only the using directives they actually need. No issues identified across any applicable review dimension.

[Copilot]

Review details

Suppressed comments (1)

src/Platform/Microsoft.Testing.Platform/OutputDevice/Terminal/TerminalTestReporter.cs:18

• The file inventory no longer matches the PR description: the implementation uses TerminalTestReporter.TestDiscovery.cs (not Discovery.cs), and AppendRetrySummaryLines remains in Summary.cs, making the actual Summary/FlakyTests sizes 248/83 rather than the documented 222/109. Since the downstream vendoring note depends on exact paths, please update the PR table and split rationale to reflect the committed layout, or move/rename the files to match it.

/// <c>TestDiscovery</c> (per-test execution and discovery output), <c>Summary</c> (the post-run verdict and counts),
/// <c>FlakyTests</c> and <c>SlowestTests</c> (the optional summary sections), <c>Coverage</c> (code-coverage and

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Copilot]

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Amaury Levé (Evangelink)]

Fixes#10367

TerminalTestReporter.Summary.cs had grown to 715 lines and mixed several unrelated concerns. This splits it along the existing logical boundaries, following the established TerminalTestReporter.<Concern>.cs convention.

File	Contents	Lines
TerminalTestReporter.Summary.cs(trimmed)	AppendTestRunSummary, AppendRetrySummaryLines	248
TerminalTestReporter.Coverage.cs(new)	AppendCoverageSummary (internal + private), FormatThresholdPercentages, GetCoverage*Label helpers	204
TerminalTestReporter.TestDiscovery.cs(new)	TestDiscovered (both overloads), AppendTestDiscoverySummary	134
TerminalTestReporter.FlakyTests.cs(new)	AppendFlakyTests, AppendFlakyTestLine	83
TerminalTestReporter.SlowestTests.cs(new)	AppendSlowestTests, AppendSlowestTestLine	79

Two deviations from the issue text, both deliberate:

• Five files, not three. The issue required every file be under 350 lines, but its own 3-way split leaves the trimmed Summary.cs at ~394 lines. Breaking out the flaky and slowest sections is what actually satisfies the stated criterion, and SlowestTests.cs at 79 lines is in line with the existing ErroredAssemblies.cs at 75.
• TestDiscovery.cs, not Discovery.cs, so it pairs with the existing TerminalTestReporter.TestCompletion.cs — the mirror concern.

AppendRetrySummaryLines stays in Summary.cs: it emits the flaky: / retried: counter lines inline between the skipped count and the duration, so it belongs with the rest of the counter block rather than with the separate "Flaky tests" listing.

Also adds a <remarks> map of the partials to the type doc on TerminalTestReporter.cs, following the precedent in TrxResultStreamingStore.cs. At 13 partials the type had no signpost for where anything lives.

Not a behavior change

No member body was modified. Verified mechanically rather than by eye: the 606 non-empty class-body lines of the original file and of the five files replacing it are an identical multiset with zero diffs, and a per-member brace-depth chunker matches all 17 members byte-for-byte. Two private helpers changed position relative to the whole file, each moving adjacent to its sole caller — AppendSlowestTestLine (previously sitting after AppendFlakyTestLine) and AppendRetrySummaryLines. The only other non-move change is narrowing each file's using set; note that the issue's guideline #5 ("no new using directives needed, all files share the same using set as today") is wrong — copying all three usings everywhere would trip IDE0005, which is warning in .editorconfig with EnforceCodeStyleInBuild=true.

Note for downstream: dotnet/sdk

This reporter source is hard-forked into dotnet/sdk, whose eng/vendored-files.json tracks each partial individually (I checked — it lists TerminalTestReporter.cs, .ErroredAssemblies.cs, .Formatting.cs, .Handshake.cs, .Lifecycle.cs, .Messaging.cs, .Summary.cs, .TestCompletion.cs … each with "scope": "reporter partial").

TerminalReporterContract.props globs *.cs, so nothing needed to change on our side. But the four new paths are absent from the SDK manifest, so until it is updated, edits to the coverage / discovery / flaky / slowest code would be invisible to the SDK's drift workflow. The shrinking of Summary.cs will fire that workflow, so it should get noticed — tracked in #10390 regardless.

Validation

• Microsoft.Testing.Platform builds for net8.0 / net9.0 / netstandard2.0 — 0 warnings, which is what proves the using sets are exactly minimal.
• Microsoft.Testing.Platform.UnitTests — passing on net8.0, net9.0, net462.
• Microsoft.Testing.Platform.TerminalReporterContract.UnitTests — passing on net8.0 and net9.0, confirming the files still compile as a standalone shared-source consumer with no platform reference.

[Copilot]

Pull request overview

Splits the oversized terminal reporter summary into focused partial-class files without changing behavior.

Changes:

• Separates coverage and discovery reporting.
• Extracts flaky/retry and slowest-test rendering.
• Keeps all files below 350 lines.

Show a summary per file

File	Description
TerminalTestReporter.Summary.cs	Retains run-summary orchestration.
TerminalTestReporter.Coverage.cs	Contains coverage summary rendering.
TerminalTestReporter.Discovery.cs	Contains discovery tracking and summaries.
TerminalTestReporter.FlakyTests.cs	Contains retry and flaky-test output.
TerminalTestReporter.SlowestTests.cs	Contains slowest-test output.

Review details

• Files reviewed: 5/5 changed files
• Comments generated: 0
• Review effort level: Balanced

[github-actions]

Note

🤖 Automated review by GitHub Copilot. Generated by the Expert Code Review workflow. To request a follow-up action, reply by tagging @copilot directly.

Expert Review Summary

Verdict: No issues found ✅

This is a pure code-move refactoring — methods were relocated from TerminalTestReporter.Summary.cs into four new partial class files (Coverage, Discovery, FlakyTests, SlowestTests) with no behavioral changes.

Dimension	Result
Threading & Concurrency	LGTM — no new shared state or synchronization changes
Public API & Binary Compatibility	LGTM — all moved members are internal or private; no public API surface change
Performance & Allocations	LGTM — identical code paths
Cross-TFM Compatibility	LGTM — no new conditional compilation or TFM-specific code
Build Infrastructure	LGTM — *.cs glob picks up new files automatically
Scope & PR Discipline	LGTM — clean separation along logical boundaries, verified line-identical
Localization & Resources	LGTM — using sets correctly narrowed per file
Code Structure	LGTM — follows established TerminalTestReporter.<x>.cs convention

All new files correctly declare [UnsupportedOSPlatform("browser")] internal sealed partial class TerminalTestReporter and include only the using directives they actually need. No issues identified across any applicable review dimension.

[Copilot]

Review details

Suppressed comments (1)

src/Platform/Microsoft.Testing.Platform/OutputDevice/Terminal/TerminalTestReporter.cs:18

• The file inventory no longer matches the PR description: the implementation uses TerminalTestReporter.TestDiscovery.cs (not Discovery.cs), and AppendRetrySummaryLines remains in Summary.cs, making the actual Summary/FlakyTests sizes 248/83 rather than the documented 222/109. Since the downstream vendoring note depends on exact paths, please update the PR table and split rationale to reflect the committed layout, or move/rename the files to match it.

/// <c>TestDiscovery</c> (per-test execution and discovery output), <c>Summary</c> (the post-run verdict and counts),
/// <c>FlakyTests</c> and <c>SlowestTests</c> (the optional summary sections), <c>Coverage</c> (code-coverage and

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Copilot]

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Amaury Levé (Evangelink)]

Fixes#10367

TerminalTestReporter.Summary.cs had grown to 715 lines and mixed several unrelated concerns. This splits it along the existing logical boundaries, following the established TerminalTestReporter.<Concern>.cs convention.

File	Contents	Lines
TerminalTestReporter.Summary.cs(trimmed)	AppendTestRunSummary, AppendRetrySummaryLines	248
TerminalTestReporter.Coverage.cs(new)	AppendCoverageSummary (internal + private), FormatThresholdPercentages, GetCoverage*Label helpers	204
TerminalTestReporter.TestDiscovery.cs(new)	TestDiscovered (both overloads), AppendTestDiscoverySummary	134
TerminalTestReporter.FlakyTests.cs(new)	AppendFlakyTests, AppendFlakyTestLine	83
TerminalTestReporter.SlowestTests.cs(new)	AppendSlowestTests, AppendSlowestTestLine	79

Two deviations from the issue text, both deliberate:

• Five files, not three. The issue required every file be under 350 lines, but its own 3-way split leaves the trimmed Summary.cs at ~394 lines. Breaking out the flaky and slowest sections is what actually satisfies the stated criterion, and SlowestTests.cs at 79 lines is in line with the existing ErroredAssemblies.cs at 75.
• TestDiscovery.cs, not Discovery.cs, so it pairs with the existing TerminalTestReporter.TestCompletion.cs — the mirror concern.

AppendRetrySummaryLines stays in Summary.cs: it emits the flaky: / retried: counter lines inline between the skipped count and the duration, so it belongs with the rest of the counter block rather than with the separate "Flaky tests" listing.

Also adds a <remarks> map of the partials to the type doc on TerminalTestReporter.cs, following the precedent in TrxResultStreamingStore.cs. At 13 partials the type had no signpost for where anything lives.

Not a behavior change

No member body was modified. Verified mechanically rather than by eye: the 606 non-empty class-body lines of the original file and of the five files replacing it are an identical multiset with zero diffs, and a per-member brace-depth chunker matches all 17 members byte-for-byte. Two private helpers changed position relative to the whole file, each moving adjacent to its sole caller — AppendSlowestTestLine (previously sitting after AppendFlakyTestLine) and AppendRetrySummaryLines. The only other non-move change is narrowing each file's using set; note that the issue's guideline #5 ("no new using directives needed, all files share the same using set as today") is wrong — copying all three usings everywhere would trip IDE0005, which is warning in .editorconfig with EnforceCodeStyleInBuild=true.

Note for downstream: dotnet/sdk

This reporter source is hard-forked into dotnet/sdk, whose eng/vendored-files.json tracks each partial individually (I checked — it lists TerminalTestReporter.cs, .ErroredAssemblies.cs, .Formatting.cs, .Handshake.cs, .Lifecycle.cs, .Messaging.cs, .Summary.cs, .TestCompletion.cs … each with "scope": "reporter partial").

TerminalReporterContract.props globs *.cs, so nothing needed to change on our side. But the four new paths are absent from the SDK manifest, so until it is updated, edits to the coverage / discovery / flaky / slowest code would be invisible to the SDK's drift workflow. The shrinking of Summary.cs will fire that workflow, so it should get noticed — tracked in #10390 regardless.

Validation

• Microsoft.Testing.Platform builds for net8.0 / net9.0 / netstandard2.0 — 0 warnings, which is what proves the using sets are exactly minimal.
• Microsoft.Testing.Platform.UnitTests — passing on net8.0, net9.0, net462.
• Microsoft.Testing.Platform.TerminalReporterContract.UnitTests — passing on net8.0 and net9.0, confirming the files still compile as a standalone shared-source consumer with no platform reference.

[Copilot]

Pull request overview

Splits the oversized terminal reporter summary into focused partial-class files without changing behavior.

Changes:

• Separates coverage and discovery reporting.
• Extracts flaky/retry and slowest-test rendering.
• Keeps all files below 350 lines.

Show a summary per file

File	Description
TerminalTestReporter.Summary.cs	Retains run-summary orchestration.
TerminalTestReporter.Coverage.cs	Contains coverage summary rendering.
TerminalTestReporter.Discovery.cs	Contains discovery tracking and summaries.
TerminalTestReporter.FlakyTests.cs	Contains retry and flaky-test output.
TerminalTestReporter.SlowestTests.cs	Contains slowest-test output.

Review details

• Files reviewed: 5/5 changed files
• Comments generated: 0
• Review effort level: Balanced

[github-actions]

Note

🤖 Automated review by GitHub Copilot. Generated by the Expert Code Review workflow. To request a follow-up action, reply by tagging @copilot directly.

Expert Review Summary

Verdict: No issues found ✅

This is a pure code-move refactoring — methods were relocated from TerminalTestReporter.Summary.cs into four new partial class files (Coverage, Discovery, FlakyTests, SlowestTests) with no behavioral changes.

Dimension	Result
Threading & Concurrency	LGTM — no new shared state or synchronization changes
Public API & Binary Compatibility	LGTM — all moved members are internal or private; no public API surface change
Performance & Allocations	LGTM — identical code paths
Cross-TFM Compatibility	LGTM — no new conditional compilation or TFM-specific code
Build Infrastructure	LGTM — *.cs glob picks up new files automatically
Scope & PR Discipline	LGTM — clean separation along logical boundaries, verified line-identical
Localization & Resources	LGTM — using sets correctly narrowed per file
Code Structure	LGTM — follows established TerminalTestReporter.<x>.cs convention

All new files correctly declare [UnsupportedOSPlatform("browser")] internal sealed partial class TerminalTestReporter and include only the using directives they actually need. No issues identified across any applicable review dimension.

[Copilot]

Review details

Suppressed comments (1)

src/Platform/Microsoft.Testing.Platform/OutputDevice/Terminal/TerminalTestReporter.cs:18

• The file inventory no longer matches the PR description: the implementation uses TerminalTestReporter.TestDiscovery.cs (not Discovery.cs), and AppendRetrySummaryLines remains in Summary.cs, making the actual Summary/FlakyTests sizes 248/83 rather than the documented 222/109. Since the downstream vendoring note depends on exact paths, please update the PR table and split rationale to reflect the committed layout, or move/rename the files to match it.

/// <c>TestDiscovery</c> (per-test execution and discovery output), <c>Summary</c> (the post-run verdict and counts),
/// <c>FlakyTests</c> and <c>SlowestTests</c> (the optional summary sections), <c>Coverage</c> (code-coverage and

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Copilot]

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Amaury Levé (Evangelink)]

Fixes#10367

TerminalTestReporter.Summary.cs had grown to 715 lines and mixed several unrelated concerns. This splits it along the existing logical boundaries, following the established TerminalTestReporter.<Concern>.cs convention.

File	Contents	Lines
TerminalTestReporter.Summary.cs(trimmed)	AppendTestRunSummary, AppendRetrySummaryLines	248
TerminalTestReporter.Coverage.cs(new)	AppendCoverageSummary (internal + private), FormatThresholdPercentages, GetCoverage*Label helpers	204
TerminalTestReporter.TestDiscovery.cs(new)	TestDiscovered (both overloads), AppendTestDiscoverySummary	134
TerminalTestReporter.FlakyTests.cs(new)	AppendFlakyTests, AppendFlakyTestLine	83
TerminalTestReporter.SlowestTests.cs(new)	AppendSlowestTests, AppendSlowestTestLine	79

Two deviations from the issue text, both deliberate:

• Five files, not three. The issue required every file be under 350 lines, but its own 3-way split leaves the trimmed Summary.cs at ~394 lines. Breaking out the flaky and slowest sections is what actually satisfies the stated criterion, and SlowestTests.cs at 79 lines is in line with the existing ErroredAssemblies.cs at 75.
• TestDiscovery.cs, not Discovery.cs, so it pairs with the existing TerminalTestReporter.TestCompletion.cs — the mirror concern.

AppendRetrySummaryLines stays in Summary.cs: it emits the flaky: / retried: counter lines inline between the skipped count and the duration, so it belongs with the rest of the counter block rather than with the separate "Flaky tests" listing.

Also adds a <remarks> map of the partials to the type doc on TerminalTestReporter.cs, following the precedent in TrxResultStreamingStore.cs. At 13 partials the type had no signpost for where anything lives.

Not a behavior change

No member body was modified. Verified mechanically rather than by eye: the 606 non-empty class-body lines of the original file and of the five files replacing it are an identical multiset with zero diffs, and a per-member brace-depth chunker matches all 17 members byte-for-byte. Two private helpers changed position relative to the whole file, each moving adjacent to its sole caller — AppendSlowestTestLine (previously sitting after AppendFlakyTestLine) and AppendRetrySummaryLines. The only other non-move change is narrowing each file's using set; note that the issue's guideline #5 ("no new using directives needed, all files share the same using set as today") is wrong — copying all three usings everywhere would trip IDE0005, which is warning in .editorconfig with EnforceCodeStyleInBuild=true.

Note for downstream: dotnet/sdk

This reporter source is hard-forked into dotnet/sdk, whose eng/vendored-files.json tracks each partial individually (I checked — it lists TerminalTestReporter.cs, .ErroredAssemblies.cs, .Formatting.cs, .Handshake.cs, .Lifecycle.cs, .Messaging.cs, .Summary.cs, .TestCompletion.cs … each with "scope": "reporter partial").

TerminalReporterContract.props globs *.cs, so nothing needed to change on our side. But the four new paths are absent from the SDK manifest, so until it is updated, edits to the coverage / discovery / flaky / slowest code would be invisible to the SDK's drift workflow. The shrinking of Summary.cs will fire that workflow, so it should get noticed — tracked in #10390 regardless.

Validation

• Microsoft.Testing.Platform builds for net8.0 / net9.0 / netstandard2.0 — 0 warnings, which is what proves the using sets are exactly minimal.
• Microsoft.Testing.Platform.UnitTests — passing on net8.0, net9.0, net462.
• Microsoft.Testing.Platform.TerminalReporterContract.UnitTests — passing on net8.0 and net9.0, confirming the files still compile as a standalone shared-source consumer with no platform reference.

[Copilot]

Pull request overview

Splits the oversized terminal reporter summary into focused partial-class files without changing behavior.

Changes:

• Separates coverage and discovery reporting.
• Extracts flaky/retry and slowest-test rendering.
• Keeps all files below 350 lines.

Show a summary per file

File	Description
TerminalTestReporter.Summary.cs	Retains run-summary orchestration.
TerminalTestReporter.Coverage.cs	Contains coverage summary rendering.
TerminalTestReporter.Discovery.cs	Contains discovery tracking and summaries.
TerminalTestReporter.FlakyTests.cs	Contains retry and flaky-test output.
TerminalTestReporter.SlowestTests.cs	Contains slowest-test output.

Review details

• Files reviewed: 5/5 changed files
• Comments generated: 0
• Review effort level: Balanced

[github-actions]

Note

🤖 Automated review by GitHub Copilot. Generated by the Expert Code Review workflow. To request a follow-up action, reply by tagging @copilot directly.

Expert Review Summary

Verdict: No issues found ✅

This is a pure code-move refactoring — methods were relocated from TerminalTestReporter.Summary.cs into four new partial class files (Coverage, Discovery, FlakyTests, SlowestTests) with no behavioral changes.

Dimension	Result
Threading & Concurrency	LGTM — no new shared state or synchronization changes
Public API & Binary Compatibility	LGTM — all moved members are internal or private; no public API surface change
Performance & Allocations	LGTM — identical code paths
Cross-TFM Compatibility	LGTM — no new conditional compilation or TFM-specific code
Build Infrastructure	LGTM — *.cs glob picks up new files automatically
Scope & PR Discipline	LGTM — clean separation along logical boundaries, verified line-identical
Localization & Resources	LGTM — using sets correctly narrowed per file
Code Structure	LGTM — follows established TerminalTestReporter.<x>.cs convention

All new files correctly declare [UnsupportedOSPlatform("browser")] internal sealed partial class TerminalTestReporter and include only the using directives they actually need. No issues identified across any applicable review dimension.

[Copilot]

Review details

Suppressed comments (1)

src/Platform/Microsoft.Testing.Platform/OutputDevice/Terminal/TerminalTestReporter.cs:18

• The file inventory no longer matches the PR description: the implementation uses TerminalTestReporter.TestDiscovery.cs (not Discovery.cs), and AppendRetrySummaryLines remains in Summary.cs, making the actual Summary/FlakyTests sizes 248/83 rather than the documented 222/109. Since the downstream vendoring note depends on exact paths, please update the PR table and split rationale to reflect the committed layout, or move/rename the files to match it.

/// <c>TestDiscovery</c> (per-test execution and discovery output), <c>Summary</c> (the post-run verdict and counts),
/// <c>FlakyTests</c> and <c>SlowestTests</c> (the optional summary sections), <c>Coverage</c> (code-coverage and

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Copilot]

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Amaury Levé (Evangelink)]

Fixes#10367

TerminalTestReporter.Summary.cs had grown to 715 lines and mixed several unrelated concerns. This splits it along the existing logical boundaries, following the established TerminalTestReporter.<Concern>.cs convention.

File	Contents	Lines
TerminalTestReporter.Summary.cs(trimmed)	AppendTestRunSummary, AppendRetrySummaryLines	248
TerminalTestReporter.Coverage.cs(new)	AppendCoverageSummary (internal + private), FormatThresholdPercentages, GetCoverage*Label helpers	204
TerminalTestReporter.TestDiscovery.cs(new)	TestDiscovered (both overloads), AppendTestDiscoverySummary	134
TerminalTestReporter.FlakyTests.cs(new)	AppendFlakyTests, AppendFlakyTestLine	83
TerminalTestReporter.SlowestTests.cs(new)	AppendSlowestTests, AppendSlowestTestLine	79

Two deviations from the issue text, both deliberate:

• Five files, not three. The issue required every file be under 350 lines, but its own 3-way split leaves the trimmed Summary.cs at ~394 lines. Breaking out the flaky and slowest sections is what actually satisfies the stated criterion, and SlowestTests.cs at 79 lines is in line with the existing ErroredAssemblies.cs at 75.
• TestDiscovery.cs, not Discovery.cs, so it pairs with the existing TerminalTestReporter.TestCompletion.cs — the mirror concern.

AppendRetrySummaryLines stays in Summary.cs: it emits the flaky: / retried: counter lines inline between the skipped count and the duration, so it belongs with the rest of the counter block rather than with the separate "Flaky tests" listing.

Also adds a <remarks> map of the partials to the type doc on TerminalTestReporter.cs, following the precedent in TrxResultStreamingStore.cs. At 13 partials the type had no signpost for where anything lives.

Not a behavior change

No member body was modified. Verified mechanically rather than by eye: the 606 non-empty class-body lines of the original file and of the five files replacing it are an identical multiset with zero diffs, and a per-member brace-depth chunker matches all 17 members byte-for-byte. Two private helpers changed position relative to the whole file, each moving adjacent to its sole caller — AppendSlowestTestLine (previously sitting after AppendFlakyTestLine) and AppendRetrySummaryLines. The only other non-move change is narrowing each file's using set; note that the issue's guideline #5 ("no new using directives needed, all files share the same using set as today") is wrong — copying all three usings everywhere would trip IDE0005, which is warning in .editorconfig with EnforceCodeStyleInBuild=true.

Note for downstream: dotnet/sdk

This reporter source is hard-forked into dotnet/sdk, whose eng/vendored-files.json tracks each partial individually (I checked — it lists TerminalTestReporter.cs, .ErroredAssemblies.cs, .Formatting.cs, .Handshake.cs, .Lifecycle.cs, .Messaging.cs, .Summary.cs, .TestCompletion.cs … each with "scope": "reporter partial").

TerminalReporterContract.props globs *.cs, so nothing needed to change on our side. But the four new paths are absent from the SDK manifest, so until it is updated, edits to the coverage / discovery / flaky / slowest code would be invisible to the SDK's drift workflow. The shrinking of Summary.cs will fire that workflow, so it should get noticed — tracked in #10390 regardless.

Validation

• Microsoft.Testing.Platform builds for net8.0 / net9.0 / netstandard2.0 — 0 warnings, which is what proves the using sets are exactly minimal.
• Microsoft.Testing.Platform.UnitTests — passing on net8.0, net9.0, net462.
• Microsoft.Testing.Platform.TerminalReporterContract.UnitTests — passing on net8.0 and net9.0, confirming the files still compile as a standalone shared-source consumer with no platform reference.

[Copilot]

Pull request overview

Splits the oversized terminal reporter summary into focused partial-class files without changing behavior.

Changes:

• Separates coverage and discovery reporting.
• Extracts flaky/retry and slowest-test rendering.
• Keeps all files below 350 lines.

Show a summary per file

File	Description
TerminalTestReporter.Summary.cs	Retains run-summary orchestration.
TerminalTestReporter.Coverage.cs	Contains coverage summary rendering.
TerminalTestReporter.Discovery.cs	Contains discovery tracking and summaries.
TerminalTestReporter.FlakyTests.cs	Contains retry and flaky-test output.
TerminalTestReporter.SlowestTests.cs	Contains slowest-test output.

Review details

• Files reviewed: 5/5 changed files
• Comments generated: 0
• Review effort level: Balanced

[github-actions]

Note

🤖 Automated review by GitHub Copilot. Generated by the Expert Code Review workflow. To request a follow-up action, reply by tagging @copilot directly.

Expert Review Summary

Verdict: No issues found ✅

This is a pure code-move refactoring — methods were relocated from TerminalTestReporter.Summary.cs into four new partial class files (Coverage, Discovery, FlakyTests, SlowestTests) with no behavioral changes.

Dimension	Result
Threading & Concurrency	LGTM — no new shared state or synchronization changes
Public API & Binary Compatibility	LGTM — all moved members are internal or private; no public API surface change
Performance & Allocations	LGTM — identical code paths
Cross-TFM Compatibility	LGTM — no new conditional compilation or TFM-specific code
Build Infrastructure	LGTM — *.cs glob picks up new files automatically
Scope & PR Discipline	LGTM — clean separation along logical boundaries, verified line-identical
Localization & Resources	LGTM — using sets correctly narrowed per file
Code Structure	LGTM — follows established TerminalTestReporter.<x>.cs convention

All new files correctly declare [UnsupportedOSPlatform("browser")] internal sealed partial class TerminalTestReporter and include only the using directives they actually need. No issues identified across any applicable review dimension.

[Copilot]

Review details

Suppressed comments (1)

src/Platform/Microsoft.Testing.Platform/OutputDevice/Terminal/TerminalTestReporter.cs:18

• The file inventory no longer matches the PR description: the implementation uses TerminalTestReporter.TestDiscovery.cs (not Discovery.cs), and AppendRetrySummaryLines remains in Summary.cs, making the actual Summary/FlakyTests sizes 248/83 rather than the documented 222/109. Since the downstream vendoring note depends on exact paths, please update the PR table and split rationale to reflect the committed layout, or move/rename the files to match it.

/// <c>TestDiscovery</c> (per-test execution and discovery output), <c>Summary</c> (the post-run verdict and counts),
/// <c>FlakyTests</c> and <c>SlowestTests</c> (the optional summary sections), <c>Coverage</c> (code-coverage and

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Copilot]

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 0 new
• Review effort level: Balanced