deps: Bump the testing-platform group with 4 updates

[dependabot]

Updated Microsoft.Testing.Extensions.CodeCoverage from 18.8.0 to 18.9.0.

Release notes

Sourced from Microsoft.Testing.Extensions.CodeCoverage's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Testing.Extensions.CrashDump from 2.2.3 to 2.3.2.

Release notes

Sourced from Microsoft.Testing.Extensions.CrashDump's releases.

2.3.0-preview-20220810-02

See release notes here.

2.2.10

See release notes here.

2.2.10-preview-20220414-01

See release notes here.

2.2.9

Parallel output

🙇 Shout out to @​SimonCropp, for bringing this functionality to XUnit in his https://github.com/SimonCropp/XunitContext project. And being an inspiration for implementing this.

MSTest 2.2.9 captures all Console output and attaches it to the correct test, even if you are running tests in parallel. This output is captured from your test code as well as from the tested code. And it requires no special setup.

Before

In 2.2.8, test output is scattered among tests, in our example, one unlucky test gets all the output of other tests just mixed together:

After

With 2.2.9, each output is correctly attached to the test that produced it:

Also notice that we are also capturing debug, trace and error. And we are not awaiting the FastChild method, and the output is still assigned correctly. Souce code.

Limitations

Due to the way that class and assembly initialize, and cleanup are invoked, their output will end up in the first test that run (or last for cleanup). This is unfortunately not easily fixable.

See release notes here.

2.2.8

See release notes here.

2.2.7

See release notes here.

2.2.6

See release notes here.

2.2.5

See release notes here.

2.2.4

See release notes here.

2.2.4-preview-20210331-02

See release notes here.

Commits viewable in compare view.

Updated Microsoft.Testing.Extensions.HangDump from 2.2.3 to 2.3.2.

Release notes

Sourced from Microsoft.Testing.Extensions.HangDump's releases.

2.3.0-preview-20220810-02

See release notes here.

2.2.10

See release notes here.

2.2.10-preview-20220414-01

See release notes here.

2.2.9

Parallel output

🙇 Shout out to @​SimonCropp, for bringing this functionality to XUnit in his https://github.com/SimonCropp/XunitContext project. And being an inspiration for implementing this.

MSTest 2.2.9 captures all Console output and attaches it to the correct test, even if you are running tests in parallel. This output is captured from your test code as well as from the tested code. And it requires no special setup.

Before

In 2.2.8, test output is scattered among tests, in our example, one unlucky test gets all the output of other tests just mixed together:

After

With 2.2.9, each output is correctly attached to the test that produced it:

Also notice that we are also capturing debug, trace and error. And we are not awaiting the FastChild method, and the output is still assigned correctly. Souce code.

Limitations

Due to the way that class and assembly initialize, and cleanup are invoked, their output will end up in the first test that run (or last for cleanup). This is unfortunately not easily fixable.

See release notes here.

2.2.8

See release notes here.

2.2.7

See release notes here.

2.2.6

See release notes here.

2.2.5

See release notes here.

2.2.4

See release notes here.

2.2.4-preview-20210331-02

See release notes here.

Commits viewable in compare view.

Updated Microsoft.Testing.Extensions.TrxReport from 2.2.3 to 2.3.2.

Release notes

Sourced from Microsoft.Testing.Extensions.TrxReport's releases.

2.3.0-preview-20220810-02

See release notes here.

2.2.10

See release notes here.

2.2.10-preview-20220414-01

See release notes here.

2.2.9

Parallel output

🙇 Shout out to @​SimonCropp, for bringing this functionality to XUnit in his https://github.com/SimonCropp/XunitContext project. And being an inspiration for implementing this.

MSTest 2.2.9 captures all Console output and attaches it to the correct test, even if you are running tests in parallel. This output is captured from your test code as well as from the tested code. And it requires no special setup.

Before

In 2.2.8, test output is scattered among tests, in our example, one unlucky test gets all the output of other tests just mixed together:

After

With 2.2.9, each output is correctly attached to the test that produced it:

Also notice that we are also capturing debug, trace and error. And we are not awaiting the FastChild method, and the output is still assigned correctly. Souce code.

Limitations

Due to the way that class and assembly initialize, and cleanup are invoked, their output will end up in the first test that run (or last for cleanup). This is unfortunately not easily fixable.

See release notes here.

2.2.8

See release notes here.

2.2.7

See release notes here.

2.2.6

See release notes here.

2.2.5

See release notes here.

2.2.4

See release notes here.

2.2.4-preview-20210331-02

See release notes here.

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[eiriktsarpalis]

@copilot please resolve the merge conflicts.

[Copilot]

@copilot please resolve the merge conflicts.

Resolved. Merged origin/main and kept both sets of updates: TUnit 1.59.0 (from main) and the Microsoft.Testing.Extensions bumps from this PR (TrxReport/CrashDump/HangDump → 2.3.2, CodeCoverage → 18.9.0). Build passes.

[eiriktsarpalis]

@copilot please diagnose and fix the test failures occuring on windows legs of CI.

[Copilot]

@copilot please diagnose and fix the test failures occuring on windows legs of CI.

Fixed in the latest commit. The root cause was that Microsoft.Testing.Extensions.CodeCoverage 18.9.0 introduced System.Text.Json 10.0.8 as a new transitive dependency (via its netstandard2.0 target), which bumped System.Text.Encodings.Web from 8.x (assembly 8.0.0.0) to 10.0.8 (assembly 10.0.826.23019). NuGet.Packaging 7.0.3 net472 — used by Microsoft.CodeAnalysis.Testing to download NuGet packages at test runtime — directly references System.Text.Encodings.Web 8.0.0.0. With System.Text.Json pinned to 10.0.5 in CPM, the MSBuild-generated binding redirect in the .exe.config could point to assembly 10.0.526.15411, while CodeCoverage 18.9.0 deploys 10.0.826.23019, producing a FileLoadException on the Windows net472 leg. Bumping System.Text.Json to 10.0.8 in Directory.Packages.props ensures System.Text.Encodings.Web resolves consistently to 10.0.826.23019 across the solution, keeping the generated redirect and deployed assembly in sync.

[eiriktsarpalis]

@copilot your changes didn't fix the Windows failures, witness https://github.com/eiriktsarpalis/PolyType/actions/runs/29350465080/job/87147128424?pr=476

[Copilot]

@copilot your changes didn't fix the Windows failures, witness https://github.com/eiriktsarpalis/PolyType/actions/runs/29350465080/job/87147128424?pr=476

Fixed in the latest commit. The root cause: CodeCoverage 18.9.0 added System.Text.Encodings.Web 10.0.8 (assembly version 10.0.0.8) as a new transitive dep, but NuGet.Packaging 7.0.3 (net472, pulled in by Microsoft.CodeAnalysis.Testing) internally references System.Text.Encodings.Web, Version=8.0.0.0. Without a direct reference to System.Text.Encodings.Web in the project graph, MSBuild doesn't generate a binding redirect covering that version range, so the assembly load fails at runtime.

The fix is to add System.Text.Encodings.Web 10.0.8 as an explicit PackageReference to PolyType.SourceGenerator.UnitTests.csproj (net472 only). This forces MSBuild to generate the redirect 0.0.0.0–10.0.0.8 → 10.0.0.8, which covers the 8.0.0.0 request. I also reverted the previous System.Text.Json version bump (which had no effect since that project has no direct System.Text.Json reference).

[eiriktsarpalis]

@copilot this is still failing

[Copilot]

@copilot this is still failing

Fixed in the latest commit. The root cause was that PolyType.SourceGenerator.UnitTests.csproj was missing <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects> and <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType> — properties that PolyType.Tests.csproj already had explicitly set.

Without these, MSBuild does not generate the .exe.config binding redirects for the net472 build. Microsoft.Testing.Extensions.CodeCoverage 18.9.0 added System.Text.Encodings.Web 10.0.8 and System.Text.Json 10.0.8 as new transitive dependencies (not present in 18.8.0), causing a version mismatch: NuGet.Packaging 7.0.3 (pulled in by Microsoft.CodeAnalysis.Testing) was compiled against System.Text.Encodings.Web 8.0.0.0, but the newer version deployed to the output directory had assembly version 10.0.0.8. Without the binding redirect, the CLR couldn't load it and the tests failed with FileLoadException.