Revert "Move hosting tests to XUnit 3"

[AaronRobinsonMSFT]

Reverts #120234

This change appears to have broken the boot strapped community builds.

[Copilot]

Pull Request Overview

This PR reverts the migration of hosting tests from XUnit v2 to XUnit v3, rolling back changes made in PR #120234. The revert restores the previous test infrastructure, including test runner configuration, execution commands, and build settings.

Key changes:

• Reverts test execution from native binary to dotnet test command
• Restores XUnit v2 packages and removes XUnit v3 dependencies
• Reverts HostTestContext back to TestContext class name
• Restores platform-specific test filtering using attributes instead of runtime checks

Reviewed Changes

Copilot reviewed 62 out of 62 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/installer/tests/helixpublish.proj	Reverts test execution command from native binary to dotnet test, removes runtime-specific CLI configuration
src/installer/tests/TestUtils/TestUtils.csproj	Switches XUnit packages from v3 back to v2
src/installer/tests/TestUtils/TestContext.cs	Renames HostTestContext class back to TestContext
src/installer/tests/TestUtils/*.cs	Updates references from HostTestContext to TestContext throughout utility classes
src/installer/tests/*/Tests.csproj	Removes XUnit v3 configuration properties (OutputType, RuntimeIdentifier, TestRunnerName)
src/installer/tests/HostActivation.Tests/*.cs	Updates all test references from HostTestContext to TestContext, restores [PlatformSpecific] attributes
src/installer/tests/Directory.Build.props	Reverts test runner arguments and filter syntax from XUnit v3 to v2 format
src/installer/tests/Directory.Build.targets	Removes XUnit v3-specific crash/hang dump package references

[dotnet-policy-service]

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

[AaronRobinsonMSFT]

/azp list

[azure-pipelines]

CI/CD Pipelines for this repository:

• runtime-coreclr outerloop
• runtime-coreclr jitstress
• runtime-coreclr jitstressregs
• runtime-coreclr jitstress2-jitstressregs
• runtime-coreclr gcstress0x3-gcstress0xc
• runtime-coreclr gcstress-extra
• runtime-coreclr r2r-extra
• runtime-coreclr jitstress-isas-x86
• runtime-coreclr jitstress-isas-arm
• runtime-coreclr jitstressregs-x86
• runtime-coreclr libraries-jitstressregs
• runtime-coreclr libraries-jitstress2-jitstressregs
• runtime-coreclr r2r
• runtime-coreclr runincontext
• runtime-coreclr crossgen2
• runtime-libraries-coreclr outerloop
• runtime-libraries-coreclr outerloop-windows
• runtime-libraries-coreclr outerloop-linux
• runtime-libraries-coreclr outerloop-osx
• runtime
• runtime-libraries enterprise-linux
• runtime-libraries stress-http
• runtime-libraries stress-ssl
• runtime-dev-innerloop
• runtime-coreclr crossgen2 outerloop
• coreclr-release-outerloop-nightly
• runtime-coreclr crossgen2-composite
• runtime-jit-experimental
• runtime-coreclr libraries-jitstress
• dotnet-linker-tests
• runtime-coreclr ilasm
• runtime-coreclr crossgen2-composite gcstress
• runtime-coreclr pgo
• runtime-coreclr libraries-pgo
• Antigen
• runtime-community
• Fuzzlyn
• runtime-coreclr superpmi-replay
• runtime-wasm
• runtime-coreclr superpmi-diffs
• runtime-coreclr superpmi-asmdiffs-checked-release
• runtime-extra-platforms
• jit-cfg
• runtime-wasm-perf
• runtime-llvm
• runtime-cet
• runtime-coreclr jitstress-random
• runtime-coreclr libraries-jitstress-random
• runtime-android-grpc-client-tests
• runtime-wasm-non-libtests
• runtime-android
• runtime-androidemulator
• runtime-ioslike
• runtime-ioslikesimulator
• runtime-linuxbionic
• runtime-maccatalyst
• runtime-coreclr pgostress
• runtime-coreclr jitstress-isas-avx512
• runtime-libraries-mono outerloop
• runtime-sanitized
• runtime-wasm-dbgtests
• runtime-wasm-optional
• runtime-nativeaot-outerloop
• runtime-coreclr superpmi-collect-test
• runtime-diagnostics
• runtime-interpreter
• runtime-report-green

[AaronRobinsonMSFT]

See #120234 (comment) for a follow up suggestion for hosting changes.

[Youssef1313]

@AaronRobinsonMSFT It would be nice to have more info in PR description about what exactly broke and/or why.

[AaronRobinsonMSFT]

@Youssef1313 As I stated, it is the boot strapping steps for the community builds - freebsd, loongarch and risc-v. These have dependencies on an LKG of the runtime, but those platforms don't have that. We have a partial set-up that makes those platforms run, but alas something in the hosting tests appears to have broken that. What that is is not clear to me, but this PR appeared to be the most likely culprit so I'm reverting it. My guess is this has to do with some bad assumption in the bootstrapping of those platforms rather than anything to do with the changes themselves.

See #120991 for the failing legs.

[jkotas]

My guess is this has to do with some bad assumption in the bootstrapping

• After the XUnit 3, the tests want to restore apphost for the target architecture from the nuget. This looks suspect. The tests should be testing fresh bits produced by local build, not some old published bits.
• We are building tests as part of the product build. It is unnecessary.

(Both of these issues should be fixed.)

[AaronRobinsonMSFT]

(Both of these issues should be fixed.)

@jkotas Agree. We're going to add a trigger for this with #120999 so when this fix is tried again, we can get better validation.