Fix TreeNodeFilter OR-pattern diagnostics

[Amaury Levé (Evangelink)]

Description

Partially addresses (does not fully fix) #7300. That issue reports four broken --treenode-filter patterns; this PR only improves the diagnostics and documentation for one of them and clarifies a known matching limitation that affects the other three.

Symptoms reported in #7300

#	Pattern	Observation
1	/*/*/*/(MyTest1)	Does not match a test named MyTest1
2	/*/*/*/(MyTest1)|(MyTest2)	Does not match either test
3	/*/*/*/(MyTest1|MyTest2)	Does not match either test
4	(/*/*/*/MyTest1)|(/*/*/*/MyTest2)	Crashes with a generic InvalidOperationException

Analysis

• Cases 1–3 are not a parser bug: (MyTest1) and (MyTest1\|MyTest2)do match a node whose final segment is exactly MyTest1 (see the new OrExpression_WorksForSinglePathSegmentInsideParentheses test). Path segments are matched against an anchored regex ^value$, so a literal MyTest1 will not match a node whose actual ID is MyTest1() (or anything else with extra suffix). TUnit appends method-signature info to the displayed name, so the node IDs the user is actually filtering against are most likely MyTest1(), MyTest2(), etc. — which is why every pattern with a wildcard like MyTest1* "works" while every literal one does not. This is a UX mismatch (display vs. node ID), not a TreeNodeFilter parser defect. Properly resolving it requires either action in TUnit's adapter (use stable IDs that match the displayed name) or a design change to relax literal-segment matching — both are out of scope here.
• Case 4 is a real parser bug: full-path OR like (/A/B/C/X)\|(/A/B/C/Y) hits separator processing inside parentheses and throws a generic InvalidOperationException with no guidance. This PR replaces that with an actionable message that points the user to the supported form /A/B/C/(X|Y).

Changes

• TreeNodeFilter.cs: thread the filter string into ProcessStackOperator so the "unexpected / inside parenthesized expression" error can include the filter and a suggested fix. Add grammar remarks noting that OR over a single path segment is supported but OR over full paths is not.
• PlatformResources.resx (+ all xlf): new TreeNodeFilterUnexpectedSlashOperatorInPathSegmentErrorMessage resource (the previous one is preserved for back-compat; tests use the new message).
• TreeNodeFilterTests.cs: regression tests for single-segment OR (OrExpression_WorksForSinglePathSegmentInsideParentheses), for the actionable error on full-path OR (FullPathOrInsideParenthesizedExpressions_IsNotSupported_ThrowsActionableMessage), and LiteralSegment_RequiresWildcardToMatchNodesWithAdditionalSuffix which documents (with a comment) the surprising literal-vs-suffix limitation behind cases 1–3.
• Changelog-Platform.md: entry framed as a diagnostics/docs clarification, not a behavior fix.

Validation

dotnet test Microsoft.Testing.Platform.UnitTests.csproj -c Debug --filter "FullyQualifiedName~TreeNodeFilterTests" → 46/46 passing on net9.0/net8.0/net462.

Follow-ups (not in this PR)

• The "literal segment does not match node ID with suffix" behavior (cases 1–3 of --treenode-filter pattern matching is at least non obvious, potentially errored #7300) remains as-is. Either TUnit should expose node IDs that match the displayed test name, or TreeNodeFilter should consider a relaxed/match-anywhere mode for literal segments. Leaving --treenode-filter pattern matching is at least non obvious, potentially errored #7300open for that discussion.

[Youssef Fahmy (Youssef1313)]

I have doubts that the problem here is clarity of error message. The behavior seems buggy IMO. Let's discuss offline.

[Amaury Levé (Evangelink)]

Merged latest main into the PR branch (was ~941 commits behind). The merge was clean with no conflicts. Verified the fix is still relevant — TreeNodeFilter.cs on main has not received an equivalent fix.

Verification:

• Built Microsoft.Testing.Platform.csproj (Debug): 0 warnings, 0 errors.
• Ran Microsoft.Testing.Platform.UnitTests filtered to TreeNodeFilter: 165 passed / 0 failed across net8.0, net9.0, net48.

Ready for CI re-run and review.

[Copilot]

Pull request overview

This PR clarifies TreeNodeFilter behavior for OR patterns and improves diagnostics when unsupported full-path OR expressions are parenthesized.

Changes:

• Adds regression coverage for single-segment OR patterns and exact-match behavior.
• Updates TreeNodeFilter grammar remarks and propagates filter text into parser error construction.
• Improves the unexpected slash diagnostic for parenthesized full-path OR patterns.

Show a summary per file

File	Description
test/UnitTests/Microsoft.Testing.Platform.UnitTests/Requests/TreeNodeFilterTests.cs	Adds tests for supported OR syntax and unsupported parenthesized full-path OR diagnostics.
src/Platform/Microsoft.Testing.Platform/Requests/TreeNodeFilter/TreeNodeFilter.cs	Documents OR syntax limitations and augments the unexpected slash exception message.

Copilot's findings

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

• Files reviewed: 29/29 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Reviewed the outstanding feedback and pushed bc8c8cf. Addressed the remaining actionable Copilot comment by adding the missing Changelog-Platform.md entry, then re-ran .\build.cmd successfully (0 warnings, 0 errors). I did not make further code changes for the older Youssef review because it reads as a discussion note ('Let's discuss offline') rather than concrete change guidance, and I skipped the already-handled localization thread because Evangelink had already replied there.

[Copilot]

Copilot's findings

• Files reviewed: 30/30 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

🔍 Build Failure Analysis

Summary — Build failed due to out-of-sync localization files (.xlf) after modifying the FrameworkMessages.resx resource file.

Root cause: Localization files (.xlf) out of sync with .resx changes

The PR modifies src/TestFramework/TestFramework/Resources/FrameworkMessages.resx by adding multiple new resource keys and renaming existing ones (e.g., AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary). While the corresponding .xlf localization files were updated in the PR, the Microsoft.DotNet.XliffTasks build validation detected that they are still out of sync with the source .resx file.

The XliffTasks validation enforces that all localization files must be perfectly synchronized with the source resource file to prevent translation drift in CI/official builds.

Affected files / errors

• src/TestFramework/TestFramework/TestFramework.csproj:net8.0 — 'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'
• src/TestFramework/TestFramework/TestFramework.csproj:net9.0 — same error
• src/TestFramework/TestFramework/TestFramework.csproj:netstandard2.0 — same error

Resource keys modified in FrameworkMessages.resx:

• Renamed: AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary
• Renamed: AreNotEqualDeltaFailMsg → AreNotEqualDeltaFailedSummary
• Renamed: HasCountFailMsg → HasCountFailedSummary
• Renamed: IsNotEmptyFailMsg → IsNotEmptyFailedSummary
• Added: AreNotSequenceEqualInAnyOrderFailedSummary, AreNotSequenceEqualInOrderFailedSummary, AreSequenceEqualInAnyOrderFailedSummary, AreSequenceEqualInOrderFailedSummary, and many more new resource keys

Proposed fix

Run the UpdateXlf MSBuild target to regenerate all .xlf files from the source .resx file:

dotnet build src/TestFramework/TestFramework/TestFramework.csproj /t:UpdateXlf

This will update all 13 localization files:

• FrameworkMessages.cs.xlf (Czech)
• FrameworkMessages.de.xlf (German)
• FrameworkMessages.es.xlf (Spanish)
• FrameworkMessages.fr.xlf (French)
• FrameworkMessages.it.xlf (Italian)
• FrameworkMessages.ja.xlf (Japanese)
• FrameworkMessages.ko.xlf (Korean)
• FrameworkMessages.pl.xlf (Polish)
• FrameworkMessages.pt-BR.xlf (Portuguese-Brazil)
• FrameworkMessages.ru.xlf (Russian)
• FrameworkMessages.tr.xlf (Turkish)
• FrameworkMessages.zh-Hans.xlf (Simplified Chinese)
• FrameworkMessages.zh-Hant.xlf (Traditional Chinese)

After running the command, commit the updated .xlf files and push to this PR.

---

Build overview

Configuration: Debug
Exit code: 1 (failure)
Failed target: Build (XliffTasks validation)
Projects affected: TestFramework.csproj (all target frameworks: net8.0, net9.0, netstandard2.0)

All MSBuild errors (3)

Code	Project	File:Line	Message
(XliffTasks)	TestFramework.csproj::net8.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::net9.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::netstandard2.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...

---

_{🤖 Generated by the Build Failure Analysis workflow using binlog analysis · commit 948f3bd}

Generated by Build Failure Analysis for issue #7415 · ● 5.3M · ◷

[Copilot]

Copilot's findings

• Files reviewed: 25/25 changed files
• Comments generated: 3

[Copilot]

Copilot's findings

• Files reviewed: 17/17 changed files
• Comments generated: 0 new

[Amaury Levé (Evangelink)]

Description

Partially addresses (does not fully fix) #7300. That issue reports four broken --treenode-filter patterns; this PR only improves the diagnostics and documentation for one of them and clarifies a known matching limitation that affects the other three.

Symptoms reported in #7300

#	Pattern	Observation
1	/*/*/*/(MyTest1)	Does not match a test named MyTest1
2	/*/*/*/(MyTest1)|(MyTest2)	Does not match either test
3	/*/*/*/(MyTest1|MyTest2)	Does not match either test
4	(/*/*/*/MyTest1)|(/*/*/*/MyTest2)	Crashes with a generic InvalidOperationException

Analysis

• Cases 1–3 are not a parser bug: (MyTest1) and (MyTest1\|MyTest2)do match a node whose final segment is exactly MyTest1 (see the new OrExpression_WorksForSinglePathSegmentInsideParentheses test). Path segments are matched against an anchored regex ^value$, so a literal MyTest1 will not match a node whose actual ID is MyTest1() (or anything else with extra suffix). TUnit appends method-signature info to the displayed name, so the node IDs the user is actually filtering against are most likely MyTest1(), MyTest2(), etc. — which is why every pattern with a wildcard like MyTest1* "works" while every literal one does not. This is a UX mismatch (display vs. node ID), not a TreeNodeFilter parser defect. Properly resolving it requires either action in TUnit's adapter (use stable IDs that match the displayed name) or a design change to relax literal-segment matching — both are out of scope here.
• Case 4 is a real parser bug: full-path OR like (/A/B/C/X)\|(/A/B/C/Y) hits separator processing inside parentheses and throws a generic InvalidOperationException with no guidance. This PR replaces that with an actionable message that points the user to the supported form /A/B/C/(X|Y).

Changes

• TreeNodeFilter.cs: thread the filter string into ProcessStackOperator so the "unexpected / inside parenthesized expression" error can include the filter and a suggested fix. Add grammar remarks noting that OR over a single path segment is supported but OR over full paths is not.
• PlatformResources.resx (+ all xlf): new TreeNodeFilterUnexpectedSlashOperatorInPathSegmentErrorMessage resource (the previous one is preserved for back-compat; tests use the new message).
• TreeNodeFilterTests.cs: regression tests for single-segment OR (OrExpression_WorksForSinglePathSegmentInsideParentheses), for the actionable error on full-path OR (FullPathOrInsideParenthesizedExpressions_IsNotSupported_ThrowsActionableMessage), and LiteralSegment_RequiresWildcardToMatchNodesWithAdditionalSuffix which documents (with a comment) the surprising literal-vs-suffix limitation behind cases 1–3.
• Changelog-Platform.md: entry framed as a diagnostics/docs clarification, not a behavior fix.

Validation

dotnet test Microsoft.Testing.Platform.UnitTests.csproj -c Debug --filter "FullyQualifiedName~TreeNodeFilterTests" → 46/46 passing on net9.0/net8.0/net462.

Follow-ups (not in this PR)

• The "literal segment does not match node ID with suffix" behavior (cases 1–3 of --treenode-filter pattern matching is at least non obvious, potentially errored #7300) remains as-is. Either TUnit should expose node IDs that match the displayed test name, or TreeNodeFilter should consider a relaxed/match-anywhere mode for literal segments. Leaving --treenode-filter pattern matching is at least non obvious, potentially errored #7300open for that discussion.

[Youssef Fahmy (Youssef1313)]

I have doubts that the problem here is clarity of error message. The behavior seems buggy IMO. Let's discuss offline.

[Amaury Levé (Evangelink)]

Merged latest main into the PR branch (was ~941 commits behind). The merge was clean with no conflicts. Verified the fix is still relevant — TreeNodeFilter.cs on main has not received an equivalent fix.

Verification:

• Built Microsoft.Testing.Platform.csproj (Debug): 0 warnings, 0 errors.
• Ran Microsoft.Testing.Platform.UnitTests filtered to TreeNodeFilter: 165 passed / 0 failed across net8.0, net9.0, net48.

Ready for CI re-run and review.

[Copilot]

Pull request overview

This PR clarifies TreeNodeFilter behavior for OR patterns and improves diagnostics when unsupported full-path OR expressions are parenthesized.

Changes:

• Adds regression coverage for single-segment OR patterns and exact-match behavior.
• Updates TreeNodeFilter grammar remarks and propagates filter text into parser error construction.
• Improves the unexpected slash diagnostic for parenthesized full-path OR patterns.

Show a summary per file

File	Description
test/UnitTests/Microsoft.Testing.Platform.UnitTests/Requests/TreeNodeFilterTests.cs	Adds tests for supported OR syntax and unsupported parenthesized full-path OR diagnostics.
src/Platform/Microsoft.Testing.Platform/Requests/TreeNodeFilter/TreeNodeFilter.cs	Documents OR syntax limitations and augments the unexpected slash exception message.

Copilot's findings

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

• Files reviewed: 29/29 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Reviewed the outstanding feedback and pushed bc8c8cf. Addressed the remaining actionable Copilot comment by adding the missing Changelog-Platform.md entry, then re-ran .\build.cmd successfully (0 warnings, 0 errors). I did not make further code changes for the older Youssef review because it reads as a discussion note ('Let's discuss offline') rather than concrete change guidance, and I skipped the already-handled localization thread because Evangelink had already replied there.

[Copilot]

Copilot's findings

• Files reviewed: 30/30 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

🔍 Build Failure Analysis

Summary — Build failed due to out-of-sync localization files (.xlf) after modifying the FrameworkMessages.resx resource file.

Root cause: Localization files (.xlf) out of sync with .resx changes

The PR modifies src/TestFramework/TestFramework/Resources/FrameworkMessages.resx by adding multiple new resource keys and renaming existing ones (e.g., AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary). While the corresponding .xlf localization files were updated in the PR, the Microsoft.DotNet.XliffTasks build validation detected that they are still out of sync with the source .resx file.

The XliffTasks validation enforces that all localization files must be perfectly synchronized with the source resource file to prevent translation drift in CI/official builds.

Affected files / errors

• src/TestFramework/TestFramework/TestFramework.csproj:net8.0 — 'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'
• src/TestFramework/TestFramework/TestFramework.csproj:net9.0 — same error
• src/TestFramework/TestFramework/TestFramework.csproj:netstandard2.0 — same error

Resource keys modified in FrameworkMessages.resx:

• Renamed: AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary
• Renamed: AreNotEqualDeltaFailMsg → AreNotEqualDeltaFailedSummary
• Renamed: HasCountFailMsg → HasCountFailedSummary
• Renamed: IsNotEmptyFailMsg → IsNotEmptyFailedSummary
• Added: AreNotSequenceEqualInAnyOrderFailedSummary, AreNotSequenceEqualInOrderFailedSummary, AreSequenceEqualInAnyOrderFailedSummary, AreSequenceEqualInOrderFailedSummary, and many more new resource keys

Proposed fix

Run the UpdateXlf MSBuild target to regenerate all .xlf files from the source .resx file:

dotnet build src/TestFramework/TestFramework/TestFramework.csproj /t:UpdateXlf

This will update all 13 localization files:

• FrameworkMessages.cs.xlf (Czech)
• FrameworkMessages.de.xlf (German)
• FrameworkMessages.es.xlf (Spanish)
• FrameworkMessages.fr.xlf (French)
• FrameworkMessages.it.xlf (Italian)
• FrameworkMessages.ja.xlf (Japanese)
• FrameworkMessages.ko.xlf (Korean)
• FrameworkMessages.pl.xlf (Polish)
• FrameworkMessages.pt-BR.xlf (Portuguese-Brazil)
• FrameworkMessages.ru.xlf (Russian)
• FrameworkMessages.tr.xlf (Turkish)
• FrameworkMessages.zh-Hans.xlf (Simplified Chinese)
• FrameworkMessages.zh-Hant.xlf (Traditional Chinese)

After running the command, commit the updated .xlf files and push to this PR.

---

Build overview

Configuration: Debug
Exit code: 1 (failure)
Failed target: Build (XliffTasks validation)
Projects affected: TestFramework.csproj (all target frameworks: net8.0, net9.0, netstandard2.0)

All MSBuild errors (3)

Code	Project	File:Line	Message
(XliffTasks)	TestFramework.csproj::net8.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::net9.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::netstandard2.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...

---

_{🤖 Generated by the Build Failure Analysis workflow using binlog analysis · commit 948f3bd}

Generated by Build Failure Analysis for issue #7415 · ● 5.3M · ◷

[Copilot]

Copilot's findings

• Files reviewed: 25/25 changed files
• Comments generated: 3

[Copilot]

Copilot's findings

• Files reviewed: 17/17 changed files
• Comments generated: 0 new

[Amaury Levé (Evangelink)]

Description

Partially addresses (does not fully fix) #7300. That issue reports four broken --treenode-filter patterns; this PR only improves the diagnostics and documentation for one of them and clarifies a known matching limitation that affects the other three.

Symptoms reported in #7300

#	Pattern	Observation
1	/*/*/*/(MyTest1)	Does not match a test named MyTest1
2	/*/*/*/(MyTest1)|(MyTest2)	Does not match either test
3	/*/*/*/(MyTest1|MyTest2)	Does not match either test
4	(/*/*/*/MyTest1)|(/*/*/*/MyTest2)	Crashes with a generic InvalidOperationException

Analysis

• Cases 1–3 are not a parser bug: (MyTest1) and (MyTest1\|MyTest2)do match a node whose final segment is exactly MyTest1 (see the new OrExpression_WorksForSinglePathSegmentInsideParentheses test). Path segments are matched against an anchored regex ^value$, so a literal MyTest1 will not match a node whose actual ID is MyTest1() (or anything else with extra suffix). TUnit appends method-signature info to the displayed name, so the node IDs the user is actually filtering against are most likely MyTest1(), MyTest2(), etc. — which is why every pattern with a wildcard like MyTest1* "works" while every literal one does not. This is a UX mismatch (display vs. node ID), not a TreeNodeFilter parser defect. Properly resolving it requires either action in TUnit's adapter (use stable IDs that match the displayed name) or a design change to relax literal-segment matching — both are out of scope here.
• Case 4 is a real parser bug: full-path OR like (/A/B/C/X)\|(/A/B/C/Y) hits separator processing inside parentheses and throws a generic InvalidOperationException with no guidance. This PR replaces that with an actionable message that points the user to the supported form /A/B/C/(X|Y).

Changes

• TreeNodeFilter.cs: thread the filter string into ProcessStackOperator so the "unexpected / inside parenthesized expression" error can include the filter and a suggested fix. Add grammar remarks noting that OR over a single path segment is supported but OR over full paths is not.
• PlatformResources.resx (+ all xlf): new TreeNodeFilterUnexpectedSlashOperatorInPathSegmentErrorMessage resource (the previous one is preserved for back-compat; tests use the new message).
• TreeNodeFilterTests.cs: regression tests for single-segment OR (OrExpression_WorksForSinglePathSegmentInsideParentheses), for the actionable error on full-path OR (FullPathOrInsideParenthesizedExpressions_IsNotSupported_ThrowsActionableMessage), and LiteralSegment_RequiresWildcardToMatchNodesWithAdditionalSuffix which documents (with a comment) the surprising literal-vs-suffix limitation behind cases 1–3.
• Changelog-Platform.md: entry framed as a diagnostics/docs clarification, not a behavior fix.

Validation

dotnet test Microsoft.Testing.Platform.UnitTests.csproj -c Debug --filter "FullyQualifiedName~TreeNodeFilterTests" → 46/46 passing on net9.0/net8.0/net462.

Follow-ups (not in this PR)

• The "literal segment does not match node ID with suffix" behavior (cases 1–3 of --treenode-filter pattern matching is at least non obvious, potentially errored #7300) remains as-is. Either TUnit should expose node IDs that match the displayed test name, or TreeNodeFilter should consider a relaxed/match-anywhere mode for literal segments. Leaving --treenode-filter pattern matching is at least non obvious, potentially errored #7300open for that discussion.

[Youssef Fahmy (Youssef1313)]

I have doubts that the problem here is clarity of error message. The behavior seems buggy IMO. Let's discuss offline.

[Amaury Levé (Evangelink)]

Merged latest main into the PR branch (was ~941 commits behind). The merge was clean with no conflicts. Verified the fix is still relevant — TreeNodeFilter.cs on main has not received an equivalent fix.

Verification:

• Built Microsoft.Testing.Platform.csproj (Debug): 0 warnings, 0 errors.
• Ran Microsoft.Testing.Platform.UnitTests filtered to TreeNodeFilter: 165 passed / 0 failed across net8.0, net9.0, net48.

Ready for CI re-run and review.

[Copilot]

Pull request overview

This PR clarifies TreeNodeFilter behavior for OR patterns and improves diagnostics when unsupported full-path OR expressions are parenthesized.

Changes:

• Adds regression coverage for single-segment OR patterns and exact-match behavior.
• Updates TreeNodeFilter grammar remarks and propagates filter text into parser error construction.
• Improves the unexpected slash diagnostic for parenthesized full-path OR patterns.

Show a summary per file

File	Description
test/UnitTests/Microsoft.Testing.Platform.UnitTests/Requests/TreeNodeFilterTests.cs	Adds tests for supported OR syntax and unsupported parenthesized full-path OR diagnostics.
src/Platform/Microsoft.Testing.Platform/Requests/TreeNodeFilter/TreeNodeFilter.cs	Documents OR syntax limitations and augments the unexpected slash exception message.

Copilot's findings

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

• Files reviewed: 29/29 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Reviewed the outstanding feedback and pushed bc8c8cf. Addressed the remaining actionable Copilot comment by adding the missing Changelog-Platform.md entry, then re-ran .\build.cmd successfully (0 warnings, 0 errors). I did not make further code changes for the older Youssef review because it reads as a discussion note ('Let's discuss offline') rather than concrete change guidance, and I skipped the already-handled localization thread because Evangelink had already replied there.

[Copilot]

Copilot's findings

• Files reviewed: 30/30 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

🔍 Build Failure Analysis

Summary — Build failed due to out-of-sync localization files (.xlf) after modifying the FrameworkMessages.resx resource file.

Root cause: Localization files (.xlf) out of sync with .resx changes

The PR modifies src/TestFramework/TestFramework/Resources/FrameworkMessages.resx by adding multiple new resource keys and renaming existing ones (e.g., AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary). While the corresponding .xlf localization files were updated in the PR, the Microsoft.DotNet.XliffTasks build validation detected that they are still out of sync with the source .resx file.

The XliffTasks validation enforces that all localization files must be perfectly synchronized with the source resource file to prevent translation drift in CI/official builds.

Affected files / errors

• src/TestFramework/TestFramework/TestFramework.csproj:net8.0 — 'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'
• src/TestFramework/TestFramework/TestFramework.csproj:net9.0 — same error
• src/TestFramework/TestFramework/TestFramework.csproj:netstandard2.0 — same error

Resource keys modified in FrameworkMessages.resx:

• Renamed: AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary
• Renamed: AreNotEqualDeltaFailMsg → AreNotEqualDeltaFailedSummary
• Renamed: HasCountFailMsg → HasCountFailedSummary
• Renamed: IsNotEmptyFailMsg → IsNotEmptyFailedSummary
• Added: AreNotSequenceEqualInAnyOrderFailedSummary, AreNotSequenceEqualInOrderFailedSummary, AreSequenceEqualInAnyOrderFailedSummary, AreSequenceEqualInOrderFailedSummary, and many more new resource keys

Proposed fix

Run the UpdateXlf MSBuild target to regenerate all .xlf files from the source .resx file:

dotnet build src/TestFramework/TestFramework/TestFramework.csproj /t:UpdateXlf

This will update all 13 localization files:

• FrameworkMessages.cs.xlf (Czech)
• FrameworkMessages.de.xlf (German)
• FrameworkMessages.es.xlf (Spanish)
• FrameworkMessages.fr.xlf (French)
• FrameworkMessages.it.xlf (Italian)
• FrameworkMessages.ja.xlf (Japanese)
• FrameworkMessages.ko.xlf (Korean)
• FrameworkMessages.pl.xlf (Polish)
• FrameworkMessages.pt-BR.xlf (Portuguese-Brazil)
• FrameworkMessages.ru.xlf (Russian)
• FrameworkMessages.tr.xlf (Turkish)
• FrameworkMessages.zh-Hans.xlf (Simplified Chinese)
• FrameworkMessages.zh-Hant.xlf (Traditional Chinese)

After running the command, commit the updated .xlf files and push to this PR.

---

Build overview

Configuration: Debug
Exit code: 1 (failure)
Failed target: Build (XliffTasks validation)
Projects affected: TestFramework.csproj (all target frameworks: net8.0, net9.0, netstandard2.0)

All MSBuild errors (3)

Code	Project	File:Line	Message
(XliffTasks)	TestFramework.csproj::net8.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::net9.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::netstandard2.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...

---

_{🤖 Generated by the Build Failure Analysis workflow using binlog analysis · commit 948f3bd}

Generated by Build Failure Analysis for issue #7415 · ● 5.3M · ◷

[Copilot]

Copilot's findings

• Files reviewed: 25/25 changed files
• Comments generated: 3

[Copilot]

Copilot's findings

• Files reviewed: 17/17 changed files
• Comments generated: 0 new

[Amaury Levé (Evangelink)]

Description

Partially addresses (does not fully fix) #7300. That issue reports four broken --treenode-filter patterns; this PR only improves the diagnostics and documentation for one of them and clarifies a known matching limitation that affects the other three.

Symptoms reported in #7300

#	Pattern	Observation
1	/*/*/*/(MyTest1)	Does not match a test named MyTest1
2	/*/*/*/(MyTest1)|(MyTest2)	Does not match either test
3	/*/*/*/(MyTest1|MyTest2)	Does not match either test
4	(/*/*/*/MyTest1)|(/*/*/*/MyTest2)	Crashes with a generic InvalidOperationException

Analysis

• Cases 1–3 are not a parser bug: (MyTest1) and (MyTest1\|MyTest2)do match a node whose final segment is exactly MyTest1 (see the new OrExpression_WorksForSinglePathSegmentInsideParentheses test). Path segments are matched against an anchored regex ^value$, so a literal MyTest1 will not match a node whose actual ID is MyTest1() (or anything else with extra suffix). TUnit appends method-signature info to the displayed name, so the node IDs the user is actually filtering against are most likely MyTest1(), MyTest2(), etc. — which is why every pattern with a wildcard like MyTest1* "works" while every literal one does not. This is a UX mismatch (display vs. node ID), not a TreeNodeFilter parser defect. Properly resolving it requires either action in TUnit's adapter (use stable IDs that match the displayed name) or a design change to relax literal-segment matching — both are out of scope here.
• Case 4 is a real parser bug: full-path OR like (/A/B/C/X)\|(/A/B/C/Y) hits separator processing inside parentheses and throws a generic InvalidOperationException with no guidance. This PR replaces that with an actionable message that points the user to the supported form /A/B/C/(X|Y).

Changes

• TreeNodeFilter.cs: thread the filter string into ProcessStackOperator so the "unexpected / inside parenthesized expression" error can include the filter and a suggested fix. Add grammar remarks noting that OR over a single path segment is supported but OR over full paths is not.
• PlatformResources.resx (+ all xlf): new TreeNodeFilterUnexpectedSlashOperatorInPathSegmentErrorMessage resource (the previous one is preserved for back-compat; tests use the new message).
• TreeNodeFilterTests.cs: regression tests for single-segment OR (OrExpression_WorksForSinglePathSegmentInsideParentheses), for the actionable error on full-path OR (FullPathOrInsideParenthesizedExpressions_IsNotSupported_ThrowsActionableMessage), and LiteralSegment_RequiresWildcardToMatchNodesWithAdditionalSuffix which documents (with a comment) the surprising literal-vs-suffix limitation behind cases 1–3.
• Changelog-Platform.md: entry framed as a diagnostics/docs clarification, not a behavior fix.

Validation

dotnet test Microsoft.Testing.Platform.UnitTests.csproj -c Debug --filter "FullyQualifiedName~TreeNodeFilterTests" → 46/46 passing on net9.0/net8.0/net462.

Follow-ups (not in this PR)

• The "literal segment does not match node ID with suffix" behavior (cases 1–3 of --treenode-filter pattern matching is at least non obvious, potentially errored #7300) remains as-is. Either TUnit should expose node IDs that match the displayed test name, or TreeNodeFilter should consider a relaxed/match-anywhere mode for literal segments. Leaving --treenode-filter pattern matching is at least non obvious, potentially errored #7300open for that discussion.

[Youssef Fahmy (Youssef1313)]

I have doubts that the problem here is clarity of error message. The behavior seems buggy IMO. Let's discuss offline.

[Amaury Levé (Evangelink)]

Merged latest main into the PR branch (was ~941 commits behind). The merge was clean with no conflicts. Verified the fix is still relevant — TreeNodeFilter.cs on main has not received an equivalent fix.

Verification:

• Built Microsoft.Testing.Platform.csproj (Debug): 0 warnings, 0 errors.
• Ran Microsoft.Testing.Platform.UnitTests filtered to TreeNodeFilter: 165 passed / 0 failed across net8.0, net9.0, net48.

Ready for CI re-run and review.

[Copilot]

Pull request overview

This PR clarifies TreeNodeFilter behavior for OR patterns and improves diagnostics when unsupported full-path OR expressions are parenthesized.

Changes:

• Adds regression coverage for single-segment OR patterns and exact-match behavior.
• Updates TreeNodeFilter grammar remarks and propagates filter text into parser error construction.
• Improves the unexpected slash diagnostic for parenthesized full-path OR patterns.

Show a summary per file

File	Description
test/UnitTests/Microsoft.Testing.Platform.UnitTests/Requests/TreeNodeFilterTests.cs	Adds tests for supported OR syntax and unsupported parenthesized full-path OR diagnostics.
src/Platform/Microsoft.Testing.Platform/Requests/TreeNodeFilter/TreeNodeFilter.cs	Documents OR syntax limitations and augments the unexpected slash exception message.

Copilot's findings

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

• Files reviewed: 29/29 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Reviewed the outstanding feedback and pushed bc8c8cf. Addressed the remaining actionable Copilot comment by adding the missing Changelog-Platform.md entry, then re-ran .\build.cmd successfully (0 warnings, 0 errors). I did not make further code changes for the older Youssef review because it reads as a discussion note ('Let's discuss offline') rather than concrete change guidance, and I skipped the already-handled localization thread because Evangelink had already replied there.

[Copilot]

Copilot's findings

• Files reviewed: 30/30 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

🔍 Build Failure Analysis

Summary — Build failed due to out-of-sync localization files (.xlf) after modifying the FrameworkMessages.resx resource file.

Root cause: Localization files (.xlf) out of sync with .resx changes

The PR modifies src/TestFramework/TestFramework/Resources/FrameworkMessages.resx by adding multiple new resource keys and renaming existing ones (e.g., AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary). While the corresponding .xlf localization files were updated in the PR, the Microsoft.DotNet.XliffTasks build validation detected that they are still out of sync with the source .resx file.

The XliffTasks validation enforces that all localization files must be perfectly synchronized with the source resource file to prevent translation drift in CI/official builds.

Affected files / errors

• src/TestFramework/TestFramework/TestFramework.csproj:net8.0 — 'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'
• src/TestFramework/TestFramework/TestFramework.csproj:net9.0 — same error
• src/TestFramework/TestFramework/TestFramework.csproj:netstandard2.0 — same error

Resource keys modified in FrameworkMessages.resx:

• Renamed: AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary
• Renamed: AreNotEqualDeltaFailMsg → AreNotEqualDeltaFailedSummary
• Renamed: HasCountFailMsg → HasCountFailedSummary
• Renamed: IsNotEmptyFailMsg → IsNotEmptyFailedSummary
• Added: AreNotSequenceEqualInAnyOrderFailedSummary, AreNotSequenceEqualInOrderFailedSummary, AreSequenceEqualInAnyOrderFailedSummary, AreSequenceEqualInOrderFailedSummary, and many more new resource keys

Proposed fix

Run the UpdateXlf MSBuild target to regenerate all .xlf files from the source .resx file:

dotnet build src/TestFramework/TestFramework/TestFramework.csproj /t:UpdateXlf

This will update all 13 localization files:

• FrameworkMessages.cs.xlf (Czech)
• FrameworkMessages.de.xlf (German)
• FrameworkMessages.es.xlf (Spanish)
• FrameworkMessages.fr.xlf (French)
• FrameworkMessages.it.xlf (Italian)
• FrameworkMessages.ja.xlf (Japanese)
• FrameworkMessages.ko.xlf (Korean)
• FrameworkMessages.pl.xlf (Polish)
• FrameworkMessages.pt-BR.xlf (Portuguese-Brazil)
• FrameworkMessages.ru.xlf (Russian)
• FrameworkMessages.tr.xlf (Turkish)
• FrameworkMessages.zh-Hans.xlf (Simplified Chinese)
• FrameworkMessages.zh-Hant.xlf (Traditional Chinese)

After running the command, commit the updated .xlf files and push to this PR.

---

Build overview

Configuration: Debug
Exit code: 1 (failure)
Failed target: Build (XliffTasks validation)
Projects affected: TestFramework.csproj (all target frameworks: net8.0, net9.0, netstandard2.0)

All MSBuild errors (3)

Code	Project	File:Line	Message
(XliffTasks)	TestFramework.csproj::net8.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::net9.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::netstandard2.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...

---

_{🤖 Generated by the Build Failure Analysis workflow using binlog analysis · commit 948f3bd}

Generated by Build Failure Analysis for issue #7415 · ● 5.3M · ◷

[Copilot]

Copilot's findings

• Files reviewed: 25/25 changed files
• Comments generated: 3

[Copilot]

Copilot's findings

• Files reviewed: 17/17 changed files
• Comments generated: 0 new

[Amaury Levé (Evangelink)]

Description

Partially addresses (does not fully fix) #7300. That issue reports four broken --treenode-filter patterns; this PR only improves the diagnostics and documentation for one of them and clarifies a known matching limitation that affects the other three.

Symptoms reported in #7300

#	Pattern	Observation
1	/*/*/*/(MyTest1)	Does not match a test named MyTest1
2	/*/*/*/(MyTest1)|(MyTest2)	Does not match either test
3	/*/*/*/(MyTest1|MyTest2)	Does not match either test
4	(/*/*/*/MyTest1)|(/*/*/*/MyTest2)	Crashes with a generic InvalidOperationException

Analysis

• Cases 1–3 are not a parser bug: (MyTest1) and (MyTest1\|MyTest2)do match a node whose final segment is exactly MyTest1 (see the new OrExpression_WorksForSinglePathSegmentInsideParentheses test). Path segments are matched against an anchored regex ^value$, so a literal MyTest1 will not match a node whose actual ID is MyTest1() (or anything else with extra suffix). TUnit appends method-signature info to the displayed name, so the node IDs the user is actually filtering against are most likely MyTest1(), MyTest2(), etc. — which is why every pattern with a wildcard like MyTest1* "works" while every literal one does not. This is a UX mismatch (display vs. node ID), not a TreeNodeFilter parser defect. Properly resolving it requires either action in TUnit's adapter (use stable IDs that match the displayed name) or a design change to relax literal-segment matching — both are out of scope here.
• Case 4 is a real parser bug: full-path OR like (/A/B/C/X)\|(/A/B/C/Y) hits separator processing inside parentheses and throws a generic InvalidOperationException with no guidance. This PR replaces that with an actionable message that points the user to the supported form /A/B/C/(X|Y).

Changes

• TreeNodeFilter.cs: thread the filter string into ProcessStackOperator so the "unexpected / inside parenthesized expression" error can include the filter and a suggested fix. Add grammar remarks noting that OR over a single path segment is supported but OR over full paths is not.
• PlatformResources.resx (+ all xlf): new TreeNodeFilterUnexpectedSlashOperatorInPathSegmentErrorMessage resource (the previous one is preserved for back-compat; tests use the new message).
• TreeNodeFilterTests.cs: regression tests for single-segment OR (OrExpression_WorksForSinglePathSegmentInsideParentheses), for the actionable error on full-path OR (FullPathOrInsideParenthesizedExpressions_IsNotSupported_ThrowsActionableMessage), and LiteralSegment_RequiresWildcardToMatchNodesWithAdditionalSuffix which documents (with a comment) the surprising literal-vs-suffix limitation behind cases 1–3.
• Changelog-Platform.md: entry framed as a diagnostics/docs clarification, not a behavior fix.

Validation

dotnet test Microsoft.Testing.Platform.UnitTests.csproj -c Debug --filter "FullyQualifiedName~TreeNodeFilterTests" → 46/46 passing on net9.0/net8.0/net462.

Follow-ups (not in this PR)

• The "literal segment does not match node ID with suffix" behavior (cases 1–3 of --treenode-filter pattern matching is at least non obvious, potentially errored #7300) remains as-is. Either TUnit should expose node IDs that match the displayed test name, or TreeNodeFilter should consider a relaxed/match-anywhere mode for literal segments. Leaving --treenode-filter pattern matching is at least non obvious, potentially errored #7300open for that discussion.

[Youssef Fahmy (Youssef1313)]

I have doubts that the problem here is clarity of error message. The behavior seems buggy IMO. Let's discuss offline.

[Amaury Levé (Evangelink)]

Merged latest main into the PR branch (was ~941 commits behind). The merge was clean with no conflicts. Verified the fix is still relevant — TreeNodeFilter.cs on main has not received an equivalent fix.

Verification:

• Built Microsoft.Testing.Platform.csproj (Debug): 0 warnings, 0 errors.
• Ran Microsoft.Testing.Platform.UnitTests filtered to TreeNodeFilter: 165 passed / 0 failed across net8.0, net9.0, net48.

Ready for CI re-run and review.

[Copilot]

Pull request overview

This PR clarifies TreeNodeFilter behavior for OR patterns and improves diagnostics when unsupported full-path OR expressions are parenthesized.

Changes:

• Adds regression coverage for single-segment OR patterns and exact-match behavior.
• Updates TreeNodeFilter grammar remarks and propagates filter text into parser error construction.
• Improves the unexpected slash diagnostic for parenthesized full-path OR patterns.

Show a summary per file

File	Description
test/UnitTests/Microsoft.Testing.Platform.UnitTests/Requests/TreeNodeFilterTests.cs	Adds tests for supported OR syntax and unsupported parenthesized full-path OR diagnostics.
src/Platform/Microsoft.Testing.Platform/Requests/TreeNodeFilter/TreeNodeFilter.cs	Documents OR syntax limitations and augments the unexpected slash exception message.

Copilot's findings

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

• Files reviewed: 29/29 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Reviewed the outstanding feedback and pushed bc8c8cf. Addressed the remaining actionable Copilot comment by adding the missing Changelog-Platform.md entry, then re-ran .\build.cmd successfully (0 warnings, 0 errors). I did not make further code changes for the older Youssef review because it reads as a discussion note ('Let's discuss offline') rather than concrete change guidance, and I skipped the already-handled localization thread because Evangelink had already replied there.

[Copilot]

Copilot's findings

• Files reviewed: 30/30 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

🔍 Build Failure Analysis

Summary — Build failed due to out-of-sync localization files (.xlf) after modifying the FrameworkMessages.resx resource file.

Root cause: Localization files (.xlf) out of sync with .resx changes

The PR modifies src/TestFramework/TestFramework/Resources/FrameworkMessages.resx by adding multiple new resource keys and renaming existing ones (e.g., AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary). While the corresponding .xlf localization files were updated in the PR, the Microsoft.DotNet.XliffTasks build validation detected that they are still out of sync with the source .resx file.

The XliffTasks validation enforces that all localization files must be perfectly synchronized with the source resource file to prevent translation drift in CI/official builds.

Affected files / errors

• src/TestFramework/TestFramework/TestFramework.csproj:net8.0 — 'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'
• src/TestFramework/TestFramework/TestFramework.csproj:net9.0 — same error
• src/TestFramework/TestFramework/TestFramework.csproj:netstandard2.0 — same error

Resource keys modified in FrameworkMessages.resx:

• Renamed: AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary
• Renamed: AreNotEqualDeltaFailMsg → AreNotEqualDeltaFailedSummary
• Renamed: HasCountFailMsg → HasCountFailedSummary
• Renamed: IsNotEmptyFailMsg → IsNotEmptyFailedSummary
• Added: AreNotSequenceEqualInAnyOrderFailedSummary, AreNotSequenceEqualInOrderFailedSummary, AreSequenceEqualInAnyOrderFailedSummary, AreSequenceEqualInOrderFailedSummary, and many more new resource keys

Proposed fix

Run the UpdateXlf MSBuild target to regenerate all .xlf files from the source .resx file:

dotnet build src/TestFramework/TestFramework/TestFramework.csproj /t:UpdateXlf

This will update all 13 localization files:

• FrameworkMessages.cs.xlf (Czech)
• FrameworkMessages.de.xlf (German)
• FrameworkMessages.es.xlf (Spanish)
• FrameworkMessages.fr.xlf (French)
• FrameworkMessages.it.xlf (Italian)
• FrameworkMessages.ja.xlf (Japanese)
• FrameworkMessages.ko.xlf (Korean)
• FrameworkMessages.pl.xlf (Polish)
• FrameworkMessages.pt-BR.xlf (Portuguese-Brazil)
• FrameworkMessages.ru.xlf (Russian)
• FrameworkMessages.tr.xlf (Turkish)
• FrameworkMessages.zh-Hans.xlf (Simplified Chinese)
• FrameworkMessages.zh-Hant.xlf (Traditional Chinese)

After running the command, commit the updated .xlf files and push to this PR.

---

Build overview

Configuration: Debug
Exit code: 1 (failure)
Failed target: Build (XliffTasks validation)
Projects affected: TestFramework.csproj (all target frameworks: net8.0, net9.0, netstandard2.0)

All MSBuild errors (3)

Code	Project	File:Line	Message
(XliffTasks)	TestFramework.csproj::net8.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::net9.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::netstandard2.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...

---

_{🤖 Generated by the Build Failure Analysis workflow using binlog analysis · commit 948f3bd}

Generated by Build Failure Analysis for issue #7415 · ● 5.3M · ◷

[Copilot]

Copilot's findings

• Files reviewed: 25/25 changed files
• Comments generated: 3

[Copilot]

Copilot's findings

• Files reviewed: 17/17 changed files
• Comments generated: 0 new

[Amaury Levé (Evangelink)]

Description

Partially addresses (does not fully fix) #7300. That issue reports four broken --treenode-filter patterns; this PR only improves the diagnostics and documentation for one of them and clarifies a known matching limitation that affects the other three.

Symptoms reported in #7300

#	Pattern	Observation
1	/*/*/*/(MyTest1)	Does not match a test named MyTest1
2	/*/*/*/(MyTest1)|(MyTest2)	Does not match either test
3	/*/*/*/(MyTest1|MyTest2)	Does not match either test
4	(/*/*/*/MyTest1)|(/*/*/*/MyTest2)	Crashes with a generic InvalidOperationException

Analysis

• Cases 1–3 are not a parser bug: (MyTest1) and (MyTest1\|MyTest2)do match a node whose final segment is exactly MyTest1 (see the new OrExpression_WorksForSinglePathSegmentInsideParentheses test). Path segments are matched against an anchored regex ^value$, so a literal MyTest1 will not match a node whose actual ID is MyTest1() (or anything else with extra suffix). TUnit appends method-signature info to the displayed name, so the node IDs the user is actually filtering against are most likely MyTest1(), MyTest2(), etc. — which is why every pattern with a wildcard like MyTest1* "works" while every literal one does not. This is a UX mismatch (display vs. node ID), not a TreeNodeFilter parser defect. Properly resolving it requires either action in TUnit's adapter (use stable IDs that match the displayed name) or a design change to relax literal-segment matching — both are out of scope here.
• Case 4 is a real parser bug: full-path OR like (/A/B/C/X)\|(/A/B/C/Y) hits separator processing inside parentheses and throws a generic InvalidOperationException with no guidance. This PR replaces that with an actionable message that points the user to the supported form /A/B/C/(X|Y).

Changes

• TreeNodeFilter.cs: thread the filter string into ProcessStackOperator so the "unexpected / inside parenthesized expression" error can include the filter and a suggested fix. Add grammar remarks noting that OR over a single path segment is supported but OR over full paths is not.
• PlatformResources.resx (+ all xlf): new TreeNodeFilterUnexpectedSlashOperatorInPathSegmentErrorMessage resource (the previous one is preserved for back-compat; tests use the new message).
• TreeNodeFilterTests.cs: regression tests for single-segment OR (OrExpression_WorksForSinglePathSegmentInsideParentheses), for the actionable error on full-path OR (FullPathOrInsideParenthesizedExpressions_IsNotSupported_ThrowsActionableMessage), and LiteralSegment_RequiresWildcardToMatchNodesWithAdditionalSuffix which documents (with a comment) the surprising literal-vs-suffix limitation behind cases 1–3.
• Changelog-Platform.md: entry framed as a diagnostics/docs clarification, not a behavior fix.

Validation

dotnet test Microsoft.Testing.Platform.UnitTests.csproj -c Debug --filter "FullyQualifiedName~TreeNodeFilterTests" → 46/46 passing on net9.0/net8.0/net462.

Follow-ups (not in this PR)

• The "literal segment does not match node ID with suffix" behavior (cases 1–3 of --treenode-filter pattern matching is at least non obvious, potentially errored #7300) remains as-is. Either TUnit should expose node IDs that match the displayed test name, or TreeNodeFilter should consider a relaxed/match-anywhere mode for literal segments. Leaving --treenode-filter pattern matching is at least non obvious, potentially errored #7300open for that discussion.

[Youssef Fahmy (Youssef1313)]

I have doubts that the problem here is clarity of error message. The behavior seems buggy IMO. Let's discuss offline.

[Amaury Levé (Evangelink)]

Merged latest main into the PR branch (was ~941 commits behind). The merge was clean with no conflicts. Verified the fix is still relevant — TreeNodeFilter.cs on main has not received an equivalent fix.

Verification:

• Built Microsoft.Testing.Platform.csproj (Debug): 0 warnings, 0 errors.
• Ran Microsoft.Testing.Platform.UnitTests filtered to TreeNodeFilter: 165 passed / 0 failed across net8.0, net9.0, net48.

Ready for CI re-run and review.

[Copilot]

Pull request overview

This PR clarifies TreeNodeFilter behavior for OR patterns and improves diagnostics when unsupported full-path OR expressions are parenthesized.

Changes:

• Adds regression coverage for single-segment OR patterns and exact-match behavior.
• Updates TreeNodeFilter grammar remarks and propagates filter text into parser error construction.
• Improves the unexpected slash diagnostic for parenthesized full-path OR patterns.

Show a summary per file

File	Description
test/UnitTests/Microsoft.Testing.Platform.UnitTests/Requests/TreeNodeFilterTests.cs	Adds tests for supported OR syntax and unsupported parenthesized full-path OR diagnostics.
src/Platform/Microsoft.Testing.Platform/Requests/TreeNodeFilter/TreeNodeFilter.cs	Documents OR syntax limitations and augments the unexpected slash exception message.

Copilot's findings

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

• Files reviewed: 29/29 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Reviewed the outstanding feedback and pushed bc8c8cf. Addressed the remaining actionable Copilot comment by adding the missing Changelog-Platform.md entry, then re-ran .\build.cmd successfully (0 warnings, 0 errors). I did not make further code changes for the older Youssef review because it reads as a discussion note ('Let's discuss offline') rather than concrete change guidance, and I skipped the already-handled localization thread because Evangelink had already replied there.

[Copilot]

Copilot's findings

• Files reviewed: 30/30 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

🔍 Build Failure Analysis

Summary — Build failed due to out-of-sync localization files (.xlf) after modifying the FrameworkMessages.resx resource file.

Root cause: Localization files (.xlf) out of sync with .resx changes

The PR modifies src/TestFramework/TestFramework/Resources/FrameworkMessages.resx by adding multiple new resource keys and renaming existing ones (e.g., AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary). While the corresponding .xlf localization files were updated in the PR, the Microsoft.DotNet.XliffTasks build validation detected that they are still out of sync with the source .resx file.

The XliffTasks validation enforces that all localization files must be perfectly synchronized with the source resource file to prevent translation drift in CI/official builds.

Affected files / errors

• src/TestFramework/TestFramework/TestFramework.csproj:net8.0 — 'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'
• src/TestFramework/TestFramework/TestFramework.csproj:net9.0 — same error
• src/TestFramework/TestFramework/TestFramework.csproj:netstandard2.0 — same error

Resource keys modified in FrameworkMessages.resx:

• Renamed: AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary
• Renamed: AreNotEqualDeltaFailMsg → AreNotEqualDeltaFailedSummary
• Renamed: HasCountFailMsg → HasCountFailedSummary
• Renamed: IsNotEmptyFailMsg → IsNotEmptyFailedSummary
• Added: AreNotSequenceEqualInAnyOrderFailedSummary, AreNotSequenceEqualInOrderFailedSummary, AreSequenceEqualInAnyOrderFailedSummary, AreSequenceEqualInOrderFailedSummary, and many more new resource keys

Proposed fix

Run the UpdateXlf MSBuild target to regenerate all .xlf files from the source .resx file:

dotnet build src/TestFramework/TestFramework/TestFramework.csproj /t:UpdateXlf

This will update all 13 localization files:

• FrameworkMessages.cs.xlf (Czech)
• FrameworkMessages.de.xlf (German)
• FrameworkMessages.es.xlf (Spanish)
• FrameworkMessages.fr.xlf (French)
• FrameworkMessages.it.xlf (Italian)
• FrameworkMessages.ja.xlf (Japanese)
• FrameworkMessages.ko.xlf (Korean)
• FrameworkMessages.pl.xlf (Polish)
• FrameworkMessages.pt-BR.xlf (Portuguese-Brazil)
• FrameworkMessages.ru.xlf (Russian)
• FrameworkMessages.tr.xlf (Turkish)
• FrameworkMessages.zh-Hans.xlf (Simplified Chinese)
• FrameworkMessages.zh-Hant.xlf (Traditional Chinese)

After running the command, commit the updated .xlf files and push to this PR.

---

Build overview

Configuration: Debug
Exit code: 1 (failure)
Failed target: Build (XliffTasks validation)
Projects affected: TestFramework.csproj (all target frameworks: net8.0, net9.0, netstandard2.0)

All MSBuild errors (3)

Code	Project	File:Line	Message
(XliffTasks)	TestFramework.csproj::net8.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::net9.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::netstandard2.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...

---

_{🤖 Generated by the Build Failure Analysis workflow using binlog analysis · commit 948f3bd}

Generated by Build Failure Analysis for issue #7415 · ● 5.3M · ◷

[Copilot]

Copilot's findings

• Files reviewed: 25/25 changed files
• Comments generated: 3

[Copilot]

Copilot's findings

• Files reviewed: 17/17 changed files
• Comments generated: 0 new

[Amaury Levé (Evangelink)]

Description

Partially addresses (does not fully fix) #7300. That issue reports four broken --treenode-filter patterns; this PR only improves the diagnostics and documentation for one of them and clarifies a known matching limitation that affects the other three.

Symptoms reported in #7300

#	Pattern	Observation
1	/*/*/*/(MyTest1)	Does not match a test named MyTest1
2	/*/*/*/(MyTest1)|(MyTest2)	Does not match either test
3	/*/*/*/(MyTest1|MyTest2)	Does not match either test
4	(/*/*/*/MyTest1)|(/*/*/*/MyTest2)	Crashes with a generic InvalidOperationException

Analysis

• Cases 1–3 are not a parser bug: (MyTest1) and (MyTest1\|MyTest2)do match a node whose final segment is exactly MyTest1 (see the new OrExpression_WorksForSinglePathSegmentInsideParentheses test). Path segments are matched against an anchored regex ^value$, so a literal MyTest1 will not match a node whose actual ID is MyTest1() (or anything else with extra suffix). TUnit appends method-signature info to the displayed name, so the node IDs the user is actually filtering against are most likely MyTest1(), MyTest2(), etc. — which is why every pattern with a wildcard like MyTest1* "works" while every literal one does not. This is a UX mismatch (display vs. node ID), not a TreeNodeFilter parser defect. Properly resolving it requires either action in TUnit's adapter (use stable IDs that match the displayed name) or a design change to relax literal-segment matching — both are out of scope here.
• Case 4 is a real parser bug: full-path OR like (/A/B/C/X)\|(/A/B/C/Y) hits separator processing inside parentheses and throws a generic InvalidOperationException with no guidance. This PR replaces that with an actionable message that points the user to the supported form /A/B/C/(X|Y).

Changes

• TreeNodeFilter.cs: thread the filter string into ProcessStackOperator so the "unexpected / inside parenthesized expression" error can include the filter and a suggested fix. Add grammar remarks noting that OR over a single path segment is supported but OR over full paths is not.
• PlatformResources.resx (+ all xlf): new TreeNodeFilterUnexpectedSlashOperatorInPathSegmentErrorMessage resource (the previous one is preserved for back-compat; tests use the new message).
• TreeNodeFilterTests.cs: regression tests for single-segment OR (OrExpression_WorksForSinglePathSegmentInsideParentheses), for the actionable error on full-path OR (FullPathOrInsideParenthesizedExpressions_IsNotSupported_ThrowsActionableMessage), and LiteralSegment_RequiresWildcardToMatchNodesWithAdditionalSuffix which documents (with a comment) the surprising literal-vs-suffix limitation behind cases 1–3.
• Changelog-Platform.md: entry framed as a diagnostics/docs clarification, not a behavior fix.

Validation

dotnet test Microsoft.Testing.Platform.UnitTests.csproj -c Debug --filter "FullyQualifiedName~TreeNodeFilterTests" → 46/46 passing on net9.0/net8.0/net462.

Follow-ups (not in this PR)

• The "literal segment does not match node ID with suffix" behavior (cases 1–3 of --treenode-filter pattern matching is at least non obvious, potentially errored #7300) remains as-is. Either TUnit should expose node IDs that match the displayed test name, or TreeNodeFilter should consider a relaxed/match-anywhere mode for literal segments. Leaving --treenode-filter pattern matching is at least non obvious, potentially errored #7300open for that discussion.

[Youssef Fahmy (Youssef1313)]

I have doubts that the problem here is clarity of error message. The behavior seems buggy IMO. Let's discuss offline.

[Amaury Levé (Evangelink)]

Merged latest main into the PR branch (was ~941 commits behind). The merge was clean with no conflicts. Verified the fix is still relevant — TreeNodeFilter.cs on main has not received an equivalent fix.

Verification:

• Built Microsoft.Testing.Platform.csproj (Debug): 0 warnings, 0 errors.
• Ran Microsoft.Testing.Platform.UnitTests filtered to TreeNodeFilter: 165 passed / 0 failed across net8.0, net9.0, net48.

Ready for CI re-run and review.

[Copilot]

Pull request overview

This PR clarifies TreeNodeFilter behavior for OR patterns and improves diagnostics when unsupported full-path OR expressions are parenthesized.

Changes:

• Adds regression coverage for single-segment OR patterns and exact-match behavior.
• Updates TreeNodeFilter grammar remarks and propagates filter text into parser error construction.
• Improves the unexpected slash diagnostic for parenthesized full-path OR patterns.

Show a summary per file

File	Description
test/UnitTests/Microsoft.Testing.Platform.UnitTests/Requests/TreeNodeFilterTests.cs	Adds tests for supported OR syntax and unsupported parenthesized full-path OR diagnostics.
src/Platform/Microsoft.Testing.Platform/Requests/TreeNodeFilter/TreeNodeFilter.cs	Documents OR syntax limitations and augments the unexpected slash exception message.

Copilot's findings

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

• Files reviewed: 29/29 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Reviewed the outstanding feedback and pushed bc8c8cf. Addressed the remaining actionable Copilot comment by adding the missing Changelog-Platform.md entry, then re-ran .\build.cmd successfully (0 warnings, 0 errors). I did not make further code changes for the older Youssef review because it reads as a discussion note ('Let's discuss offline') rather than concrete change guidance, and I skipped the already-handled localization thread because Evangelink had already replied there.

[Copilot]

Copilot's findings

• Files reviewed: 30/30 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

🔍 Build Failure Analysis

Summary — Build failed due to out-of-sync localization files (.xlf) after modifying the FrameworkMessages.resx resource file.

Root cause: Localization files (.xlf) out of sync with .resx changes

The PR modifies src/TestFramework/TestFramework/Resources/FrameworkMessages.resx by adding multiple new resource keys and renaming existing ones (e.g., AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary). While the corresponding .xlf localization files were updated in the PR, the Microsoft.DotNet.XliffTasks build validation detected that they are still out of sync with the source .resx file.

The XliffTasks validation enforces that all localization files must be perfectly synchronized with the source resource file to prevent translation drift in CI/official builds.

Affected files / errors

• src/TestFramework/TestFramework/TestFramework.csproj:net8.0 — 'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'
• src/TestFramework/TestFramework/TestFramework.csproj:net9.0 — same error
• src/TestFramework/TestFramework/TestFramework.csproj:netstandard2.0 — same error

Resource keys modified in FrameworkMessages.resx:

• Renamed: AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary
• Renamed: AreNotEqualDeltaFailMsg → AreNotEqualDeltaFailedSummary
• Renamed: HasCountFailMsg → HasCountFailedSummary
• Renamed: IsNotEmptyFailMsg → IsNotEmptyFailedSummary
• Added: AreNotSequenceEqualInAnyOrderFailedSummary, AreNotSequenceEqualInOrderFailedSummary, AreSequenceEqualInAnyOrderFailedSummary, AreSequenceEqualInOrderFailedSummary, and many more new resource keys

Proposed fix

Run the UpdateXlf MSBuild target to regenerate all .xlf files from the source .resx file:

dotnet build src/TestFramework/TestFramework/TestFramework.csproj /t:UpdateXlf

This will update all 13 localization files:

• FrameworkMessages.cs.xlf (Czech)
• FrameworkMessages.de.xlf (German)
• FrameworkMessages.es.xlf (Spanish)
• FrameworkMessages.fr.xlf (French)
• FrameworkMessages.it.xlf (Italian)
• FrameworkMessages.ja.xlf (Japanese)
• FrameworkMessages.ko.xlf (Korean)
• FrameworkMessages.pl.xlf (Polish)
• FrameworkMessages.pt-BR.xlf (Portuguese-Brazil)
• FrameworkMessages.ru.xlf (Russian)
• FrameworkMessages.tr.xlf (Turkish)
• FrameworkMessages.zh-Hans.xlf (Simplified Chinese)
• FrameworkMessages.zh-Hant.xlf (Traditional Chinese)

After running the command, commit the updated .xlf files and push to this PR.

---

Build overview

Configuration: Debug
Exit code: 1 (failure)
Failed target: Build (XliffTasks validation)
Projects affected: TestFramework.csproj (all target frameworks: net8.0, net9.0, netstandard2.0)

All MSBuild errors (3)

Code	Project	File:Line	Message
(XliffTasks)	TestFramework.csproj::net8.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::net9.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::netstandard2.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...

---

_{🤖 Generated by the Build Failure Analysis workflow using binlog analysis · commit 948f3bd}

Generated by Build Failure Analysis for issue #7415 · ● 5.3M · ◷

[Copilot]

Copilot's findings

• Files reviewed: 25/25 changed files
• Comments generated: 3

[Copilot]

Copilot's findings

• Files reviewed: 17/17 changed files
• Comments generated: 0 new

[Amaury Levé (Evangelink)]

Description

Partially addresses (does not fully fix) #7300. That issue reports four broken --treenode-filter patterns; this PR only improves the diagnostics and documentation for one of them and clarifies a known matching limitation that affects the other three.

Symptoms reported in #7300

#	Pattern	Observation
1	/*/*/*/(MyTest1)	Does not match a test named MyTest1
2	/*/*/*/(MyTest1)|(MyTest2)	Does not match either test
3	/*/*/*/(MyTest1|MyTest2)	Does not match either test
4	(/*/*/*/MyTest1)|(/*/*/*/MyTest2)	Crashes with a generic InvalidOperationException

Analysis

• Cases 1–3 are not a parser bug: (MyTest1) and (MyTest1\|MyTest2)do match a node whose final segment is exactly MyTest1 (see the new OrExpression_WorksForSinglePathSegmentInsideParentheses test). Path segments are matched against an anchored regex ^value$, so a literal MyTest1 will not match a node whose actual ID is MyTest1() (or anything else with extra suffix). TUnit appends method-signature info to the displayed name, so the node IDs the user is actually filtering against are most likely MyTest1(), MyTest2(), etc. — which is why every pattern with a wildcard like MyTest1* "works" while every literal one does not. This is a UX mismatch (display vs. node ID), not a TreeNodeFilter parser defect. Properly resolving it requires either action in TUnit's adapter (use stable IDs that match the displayed name) or a design change to relax literal-segment matching — both are out of scope here.
• Case 4 is a real parser bug: full-path OR like (/A/B/C/X)\|(/A/B/C/Y) hits separator processing inside parentheses and throws a generic InvalidOperationException with no guidance. This PR replaces that with an actionable message that points the user to the supported form /A/B/C/(X|Y).

Changes

• TreeNodeFilter.cs: thread the filter string into ProcessStackOperator so the "unexpected / inside parenthesized expression" error can include the filter and a suggested fix. Add grammar remarks noting that OR over a single path segment is supported but OR over full paths is not.
• PlatformResources.resx (+ all xlf): new TreeNodeFilterUnexpectedSlashOperatorInPathSegmentErrorMessage resource (the previous one is preserved for back-compat; tests use the new message).
• TreeNodeFilterTests.cs: regression tests for single-segment OR (OrExpression_WorksForSinglePathSegmentInsideParentheses), for the actionable error on full-path OR (FullPathOrInsideParenthesizedExpressions_IsNotSupported_ThrowsActionableMessage), and LiteralSegment_RequiresWildcardToMatchNodesWithAdditionalSuffix which documents (with a comment) the surprising literal-vs-suffix limitation behind cases 1–3.
• Changelog-Platform.md: entry framed as a diagnostics/docs clarification, not a behavior fix.

Validation

dotnet test Microsoft.Testing.Platform.UnitTests.csproj -c Debug --filter "FullyQualifiedName~TreeNodeFilterTests" → 46/46 passing on net9.0/net8.0/net462.

Follow-ups (not in this PR)

• The "literal segment does not match node ID with suffix" behavior (cases 1–3 of --treenode-filter pattern matching is at least non obvious, potentially errored #7300) remains as-is. Either TUnit should expose node IDs that match the displayed test name, or TreeNodeFilter should consider a relaxed/match-anywhere mode for literal segments. Leaving --treenode-filter pattern matching is at least non obvious, potentially errored #7300open for that discussion.

[Youssef Fahmy (Youssef1313)]

I have doubts that the problem here is clarity of error message. The behavior seems buggy IMO. Let's discuss offline.

[Amaury Levé (Evangelink)]

Merged latest main into the PR branch (was ~941 commits behind). The merge was clean with no conflicts. Verified the fix is still relevant — TreeNodeFilter.cs on main has not received an equivalent fix.

Verification:

• Built Microsoft.Testing.Platform.csproj (Debug): 0 warnings, 0 errors.
• Ran Microsoft.Testing.Platform.UnitTests filtered to TreeNodeFilter: 165 passed / 0 failed across net8.0, net9.0, net48.

Ready for CI re-run and review.

[Copilot]

Pull request overview

This PR clarifies TreeNodeFilter behavior for OR patterns and improves diagnostics when unsupported full-path OR expressions are parenthesized.

Changes:

• Adds regression coverage for single-segment OR patterns and exact-match behavior.
• Updates TreeNodeFilter grammar remarks and propagates filter text into parser error construction.
• Improves the unexpected slash diagnostic for parenthesized full-path OR patterns.

Show a summary per file

File	Description
test/UnitTests/Microsoft.Testing.Platform.UnitTests/Requests/TreeNodeFilterTests.cs	Adds tests for supported OR syntax and unsupported parenthesized full-path OR diagnostics.
src/Platform/Microsoft.Testing.Platform/Requests/TreeNodeFilter/TreeNodeFilter.cs	Documents OR syntax limitations and augments the unexpected slash exception message.

Copilot's findings

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

• Files reviewed: 29/29 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Reviewed the outstanding feedback and pushed bc8c8cf. Addressed the remaining actionable Copilot comment by adding the missing Changelog-Platform.md entry, then re-ran .\build.cmd successfully (0 warnings, 0 errors). I did not make further code changes for the older Youssef review because it reads as a discussion note ('Let's discuss offline') rather than concrete change guidance, and I skipped the already-handled localization thread because Evangelink had already replied there.

[Copilot]

Copilot's findings

• Files reviewed: 30/30 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

🔍 Build Failure Analysis

Summary — Build failed due to out-of-sync localization files (.xlf) after modifying the FrameworkMessages.resx resource file.

Root cause: Localization files (.xlf) out of sync with .resx changes

The PR modifies src/TestFramework/TestFramework/Resources/FrameworkMessages.resx by adding multiple new resource keys and renaming existing ones (e.g., AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary). While the corresponding .xlf localization files were updated in the PR, the Microsoft.DotNet.XliffTasks build validation detected that they are still out of sync with the source .resx file.

The XliffTasks validation enforces that all localization files must be perfectly synchronized with the source resource file to prevent translation drift in CI/official builds.

Affected files / errors

• src/TestFramework/TestFramework/TestFramework.csproj:net8.0 — 'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'
• src/TestFramework/TestFramework/TestFramework.csproj:net9.0 — same error
• src/TestFramework/TestFramework/TestFramework.csproj:netstandard2.0 — same error

Resource keys modified in FrameworkMessages.resx:

• Renamed: AreEqualDeltaFailMsg → AreEqualDeltaFailedSummary
• Renamed: AreNotEqualDeltaFailMsg → AreNotEqualDeltaFailedSummary
• Renamed: HasCountFailMsg → HasCountFailedSummary
• Renamed: IsNotEmptyFailMsg → IsNotEmptyFailedSummary
• Added: AreNotSequenceEqualInAnyOrderFailedSummary, AreNotSequenceEqualInOrderFailedSummary, AreSequenceEqualInAnyOrderFailedSummary, AreSequenceEqualInOrderFailedSummary, and many more new resource keys

Proposed fix

Run the UpdateXlf MSBuild target to regenerate all .xlf files from the source .resx file:

dotnet build src/TestFramework/TestFramework/TestFramework.csproj /t:UpdateXlf

This will update all 13 localization files:

• FrameworkMessages.cs.xlf (Czech)
• FrameworkMessages.de.xlf (German)
• FrameworkMessages.es.xlf (Spanish)
• FrameworkMessages.fr.xlf (French)
• FrameworkMessages.it.xlf (Italian)
• FrameworkMessages.ja.xlf (Japanese)
• FrameworkMessages.ko.xlf (Korean)
• FrameworkMessages.pl.xlf (Polish)
• FrameworkMessages.pt-BR.xlf (Portuguese-Brazil)
• FrameworkMessages.ru.xlf (Russian)
• FrameworkMessages.tr.xlf (Turkish)
• FrameworkMessages.zh-Hans.xlf (Simplified Chinese)
• FrameworkMessages.zh-Hant.xlf (Traditional Chinese)

After running the command, commit the updated .xlf files and push to this PR.

---

Build overview

Configuration: Debug
Exit code: 1 (failure)
Failed target: Build (XliffTasks validation)
Projects affected: TestFramework.csproj (all target frameworks: net8.0, net9.0, netstandard2.0)

All MSBuild errors (3)

Code	Project	File:Line	Message
(XliffTasks)	TestFramework.csproj::net8.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::net9.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...
(XliffTasks)	TestFramework.csproj::netstandard2.0	Microsoft.DotNet.XliffTasks.targets:84	'Resources/xlf/FrameworkMessages.cs.xlf' is out-of-date with 'Resources/FrameworkMessages.resx'. Run msbuild /t:UpdateXlf to update .xlf files...

---

_{🤖 Generated by the Build Failure Analysis workflow using binlog analysis · commit 948f3bd}

Generated by Build Failure Analysis for issue #7415 · ● 5.3M · ◷

[Copilot]

Copilot's findings

• Files reviewed: 25/25 changed files
• Comments generated: 3

[Copilot]

Copilot's findings

• Files reviewed: 17/17 changed files
• Comments generated: 0 new