You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EXPERIMENT / PROTOTYPE ONLY — this pull request exists for design validation. It is not a shipping commitment, does not establish a supported package or API, and must not be interpreted as a product roadmap promise.
Pull request
Summary
This prototype adds an optional Microsoft.Testing.Platform.Browser package that runs pure-managed browser-WASM MTP applications through dotnet test, following dotnet/sdk#55906. It builds on the authenticated HTTP transport from #10143 and single-threaded browser/WASI TRX support from #10324 while keeping browser dependencies and servicing cadence out of core MTP.
Current reconciled validation inputs (2026-11-02):
verified SDK/shared runner: f7edbfedcb5319fd006078d1f9516f4a27442ddf, delivered by dotnet/sdk#56305
caller-only reconciliation: 63d157f265bff0abb1c5d5a5aeb3c32de9ecf083 (SDK pin, test-harness parsing, and evidence; no shipping-source change)
the caller pin follows that verified SDK input; the SDK's package-source pin remains the immutable TestFX revision above rather than chasing caller-only HEAD updates
Current readiness: the fresh Windows stock composition passes all 11 required cases, and the source-matched SDK Linux CI now also passes 11/11. Runtime layouts are explicitly augmented with the producer-declared Core runtimes, not unmodified shipping SDKs. Current SDK Windows and TestFX reverse-direction Windows/Linux CI remain gates; the PR stays draft and Agent merge stays paused. Historical green runs below do not establish current-head readiness.
A project opts in with a Microsoft.Testing.Platform.Browser package reference and an explicit Chromium-family executable. MTP remains authoritative for discovery, execution, filtering, progress/results, cancellation, and artifact production. The optional package owns browser/page/host lifecycle only; the browser app sends results and artifacts directly to the SDK HTTP gateway.
Design and decision record
The maintained cross-repository design discussion is dotnet/sdk#55906. The implementation boundary is:
The maintained protocol decision and field reference records the current reconciliation: upstream coverage retains serializer 15, handshake property 20, and artifact metadata field 9; browser transfer uses serializers 17/18 and browser properties 26-31. Retired experimental serializer 16 and properties 21-25 are not reused. Mixed old/new peers do not activate mismatched decoders; absent transfer capability retains the warning/suppressed-VFS-path fallback.
The package uses Playwright's private stdio protocol and never opens an unauthenticated TCP DevTools endpoint. Bootstrap bearer data is expanded from the SDK-owned response file in memory and is not placed in URLs or logs.
xHarness was investigated but not reused at runtime. Its Selenium/WebDriver server, URL query arguments, DOM tests_done, and console/result parsing conflict with direct MTP HTTP reporting. Its browser startup, container flags, retry, timeout, and cleanup experience informed this implementation.
Protocol additions are capability-gated and backward compatible:
protocol 1.5.0 handshake properties advertise HTTP control and artifact limits;
existing control serializers are reused over a second authenticated HTTP client;
artifact payloads use bounded raw TLV chunks with SDK-owned paths and quotas;
missing transfer capability remains compatibility-warning behavior, while a negotiated transfer failure is terminal.
BrowserTestingPackages.slnf is the conventional package-only build graph: eight package roots plus the non-packable MSTest.GlobalConfigsGenerator build dependency. Acceptance is built separately at evaluated NetCurrent. Package version lookups in AcceptanceTestBase are lazy, so reduced feeds do not fail on unrelated absent packages; missing or duplicate packages still fail exactly when requested.
CI uses existing capacity-backed public pools:
Windows: windows.vs2026preview.scout.amd64.open, required by the repo SDK's MSBuild 18.7 minimum and UWP package assets;
Linux: build.ubuntu.2204.amd64.open, with the SDK-owned CI-only InstallBrowser.sh prerequisite (fingerprint-verified Google signed APT repository when Chrome is absent).
No system-tool/cache deletion or SDK component omission is used.
The strict composed suite exercises normal run, --list-tests, matching/zero/project filters, managed cancellation (exit 3), intentional test failure aggregation, >1 MiB two-chunk artifact export and byte integrity, quota rejection, package/runtime layout, desktop non-interference, and process cleanup.
Historical pre-reconciliation CI evidence from TestFX build 1632026, testing merge commit f1c7147a236bb16641e85058956d91138a228f1f with SDK 66309ab55fce95ee42e5e2236c02f7371332dbf8 (not proof of the current allocation):
Linux job: passed, test run 45287224, 11/11 passed, 0 failed/incomplete/not-applicable; Chrome 155.0.8059.39; diagnostic artifact (2,075,499 bytes).
Windows job: passed, test run 45287840, 11/11 passed, 0 failed/incomplete/not-applicable; Edge 153.0.4234.48; diagnostic artifact (2,147,863 bytes).
Both downloaded TestFX artifacts pass the SDK-owned exact-11-case validator, record succeeded=true, and record exit 0 for all six composed commands.
Aligned SDK build 1632034 independently passed its browser jobs: Linux run 45287292 and Windows run 45287874, each 11/11 passed with zero failed/incomplete/not-applicable.
These were four independent green composed jobs for the earlier inputs: TestFX Windows/Linux and SDK Windows/Linux. They are retained as history, not current Linux proof. No screenshot is included because these changes concern process/protocol and physical package contracts rather than rendered UI layout; exact commands, TRX outcomes, and artifact-integrity assertions are the clearer reproducible evidence.
Validation and regression proof
Current source-matched composition
From the SDK checkout at f7edbfedcb5319fd006078d1f9516f4a27442ddf, with the restored counterpart's actual clean HEAD verified as 11b0d39f9079e5ead7b91ae5ab5161b5dcd8a147:
Result: parent exit 0; all seven recorded commands exit 0; SDK product build, fresh TestFX shipping pack, and net12 acceptance-host build each have zero warnings/errors. Windows x64, SDK 12.0.100-dev, Edge 156.0.4314.58. All 11 exact names in eng/browser-testing/required-tests.json execute and pass, zero skipped. The older btf-dd63a33d directory label is not used as source identity.
The final evidence.json, packages/manifest.json, runtime-manifest.json, and test-results/browser.trx were read independently. All eight staged package SHA-256 values and all 756 declared-runtime destination file hashes/lengths were independently rechecked after acceptance. Browser 0.1.0-dev SHA-256: 73272744AC68618B59EAF8FA6283A8F9AB714DD5A9696F4E4B9D77691C88FAB8; MTP packages 2.6.0-dev, MSTest packages 4.6.0-dev.
The layout is explicitly augmented: Core 8.0.32, 9.0.21, 10.0.13, and 11.0.0-rc.2.26504.105 come from the restored producer-declared private bootstrap. SDK/muxer/hostfxr, TFM, roll-forward, and exit/zero-result assertions are unchanged. This prerequisite is recorded as runtimeLayoutAugmented=true; it is not a claim that the shipping SDK contains every prior runtime.
BrowserPackage_DotnetTestRunsAndListsTestsThroughSdkHttpGateway passes in the stock composition, including the large two-chunk artifact integrity assertions.
Cooperative cancellation and bounded process cleanup
BrowserPackage_SdkCancellationStopsManagedBrowserRun passes; WindowsJob_CloseKillsWorkerAndSpawnedChild separately passes with both process-exit assertions retained.
Negotiated quota failure is terminal
BrowserPackage_ArtifactQuotaFailureFailsRun passes; its intentionally nonzero child is not counted as an outer failure.
Canonical culture paths and package variants
BrowserPackage_ContainsPrivateCrossPlatformPlaywrightRuntime, BrowserPackage_PackNoBuildPreservesRuntimePayload, and BrowserPackage_PackWithoutBundledNodePreservesPrivateDriverAndLicenses pass. SatellitePackagePath_NormalizesProductionMetadata separately covers leading/relative Unix and Windows metadata.
Desktop non-interference and selected executable identity
BrowserPackage_DesktopTestApplicationIsUnaffected passes with the declared runtime present; DotnetMuxer_ExplicitPathWithSpacesStartsSelectedExecutable separately passes.
The source-matched SDK Linux browser job in build 1659804 is now green. The coordinator independently reconciled actual log 91 and the downloaded Browser_Linux_x64_Attempt1 TRX/evidence: 11 distinct cases execute/pass, 0 failures/skips, all 11 recorded commands exit 0, and all eight package-manifest sources are 11b0d39f9079e5ead7b91ae5ab5161b5dcd8a147. The SDK tested merge is e6fff7ae1092ffff9b2ffb31626e75b5f157bd75, with verified parents SDK main652269386d3c0702de4e6c9a6b8495e7eef5cfbc and SDK PR head f7edbfedcb5319fd006078d1f9516f4a27442ddf; the live SDK check also reports Success. Its explicit augmented Linux runtime manifest has 753 files, not the Windows layout's 756; Core 11 RC2 libcoreclr.so SHA-256 is A5DD0CF3A4F6D36F13C3D71D3244B6457A2C510EEED7A616FC952CCFA8C28E80. SDK Windows remains in progress. This adds real counterpart Linux proof, not a TestFX current-caller CI pass.
Current CI checkpoint and caller-only correction
The actual Windows and Linux TRX/evidence from TestFX build 1659780 were downloaded independently, rather than extrapolating one platform's results to the other. Both record tested merge 030bcf378c5fbbbed766f101ccb305498f1d110d and old SDK 66309ab55fce95ee42e5e2236c02f7371332dbf8, not the final caller pin. Each executes 11 cases: 8 pass, 3 fail, 0 skip.
On both platforms, BrowserPackage_ContainsPrivateCrossPlatformPlaywrightRuntime, BrowserPackage_PackNoBuildPreservesRuntimePayload, and BrowserPackage_PackWithoutBundledNodePreservesPrivateDriverAndLicenses pass. The three prior canonical-satellite/package-variant failures are absent in this actual Linux run, not merely predicted fixed from a Windows check.
The remaining failures are exactly BrowserPackage_DotnetTestRunsAndListsTestsThroughSdkHttpGateway (missing export directory), BrowserPackage_ArtifactQuotaFailureFailsRun (child exit 0 with the explicit unsupported-artifact-export warning), and BrowserPackage_DesktopTestApplicationIsUnaffected (Core 11.0.0-rc.2.26504.105 required but only 11 RC1 present; Linux exit 150, Windows exit -2147450730). All five preceding build/evaluation commands exit 0, while browser acceptance exits 2. Published diagnostic artifacts: Linux and Windows.
Ordinary Linux separately exposes four metadata-test failures because verbose CLI output prefixes the correct property with Telemetry is: Disabled. The caller-only correction reuses the already-tested last-nonempty-line parser, preserves exact tools/net8.0/any/tr/ equality, and explicitly arranges the child setting both present and absent. It does not disable CI tracing, relax any satellite/exit assertions, change wire fields, or alter shipping source.
The same eight SatellitePackagePath_NormalizesProductionMetadata rows execute in the local harness comparison: before extraction correction, four verbose rows fail at the intended banner-versus-path assertion and four absent-setting rows pass (exit 2); afterward 8/8 pass, zero skips, exit 0. This is a test-harness reproduction, not additional production-mutation proof. Both builds below finish with 0 warnings/errors, exit 0, using the CMD-local Windows PowerShell bootstrap path. The exact metadata selector is unchanged:
The same eight rows also pass 8/8, zero skips, exit 0 with the parent process explicitly inheriting the CI-style verbose setting, proving that child absence is not accidentally inherited:
The production files remain byte-for-byte unchanged from the SDK's immutable package-source 11b0d39f9079e5ead7b91ae5ab5161b5dcd8a147. The corrected caller and test harness do not require cycling the SDK's package-source pin. Final TestFX current-head Windows/Linux and SDK Windows CI still gate readiness; the old-pin failures above are not silently reclassified as passing.
Test-value evidence
Wire capability isolation: an isolated comparison of the c22e5fd7 source restored only ServerControlTransport from 26 to 20, retaining the four new cases/assertions. It compiled cleanly and executed four cases: three intended control-capability assertion failures, one pass, zero skips, exit 2. The aligned four-case selection passes 4/4. The nested harness changed only precedence between byte-equivalent global analyzer policies; no checks were suppressed.
Missing satellites and executable quoting: retained tests first execute two intended assertion failures: 13 expected culture paths versus zero packed paths, and a deliberately launchable misparsed native executable returning 1 rather than 0. With the fixes and fresh packages, the covering six-case selection passes 6/6, zero skips.
Linux path normalization: real build 1659688 exposed tools/net8.0/any//<culture>/...; its exact package assertions were retained. At the dd63a33d production expression, four metadata cases execute: the two leading-separator cases fail on any//tr/, and two relative cases pass. The normalized 11b0d39f expression passes all four; the covering package/path selection passes 10/10. These are production-expression checks on Windows, not substituted Linux-runtime proof.
No usable control pipe: the existing StartServerControlChannelAsync_SupportedButPipeNameEmptyDoesNotCreateListener case executes/fails before the production allocation guard and executes/passes afterward with the same assertion. PID-marker publication now closes its temporary file before renaming; its real Windows containment case passes without weakening lifetime assertions. No deterministic timing-failure claim is made for that race.
The TestFX current-caller Windows/Linux jobs remain readiness gates. Build 1659688 also has a separately retained ordinary Linux Release MSB3026 shared test-layout copy failure. Its project source is unchanged, but graph/global-input changes can affect exposure; concurrent writers and PR causation are unproven. The failed-binlog/log endpoints subsequently return 404. No workaround was added, and a later passing run alone is not described as fixing that collision.
Historical focused repository validation
build.cmd -c Release -pack -projects BrowserTestingPackages.slnf -mt 0 -bl -bln BrowserTestingPackages-fresh.binlog from a new detached checkout at bbbbfd23d4de8ed70a261b52a326804492b4b037: passed, exit 0, 0 warnings/errors. Exactly eight non-symbol shipping nupkgs were produced and every nuspec repository commit matched that exact source SHA.
direct MTP run filtered to AcceptanceTestBaseTests: 1/1 passed, 0 skipped. It proves unused absent packages are not resolved, required absent packages fail with found 0, and duplicate packages fail with found 2.
direct MTP run filtered to BrowserPackage_ContainsPrivateCrossPlatformPlaywrightRuntime while Shipping contained exactly the required eight dev nupkgs: 1/1 passed, 0 skipped; the original 43-package local feed was restored afterward.
BuildDriverTests: 2/2 passed, covering nonzero build.cmd failure propagation/binlog creation and root-wrapper forwarding of -mt 0.
strict shared composed acceptance in TestFX build 1632026: Linux 11/11, Windows 11/11, no skips.
strict shared composed acceptance in SDK build 1632034: Linux 11/11, Windows 11/11, no skips.
The required-test manifest contains 11 exact TRX names and the shared validator requires every name exactly once, all Passed, zero skipped, and a valid TRX. Every generated fixture uses a unique short NuGet cache and compares all eight restored project.assets.json SHA-512 values with the staged nupkg bytes.
Immutable aligned package evidence remains at source b6c7cac92f7eeb788ae026471239ff110207bc24 under artifacts/validation/Microsoft.Testing.Platform.Browser/b6c7cac92-aligned/Shipping; the Browser nupkg SHA-256 is 2D078CB340E45A0E6C1CC5894BFF3148E29218683F36D5D038F24B3C78E67580.
At this body update, SDK Linux success is confirmed above; SDK Windows and TestFX reverse-direction/current-caller CI have not been claimed green. The PR remains draft and TestFX app maintenance remains paused. The source-matched local Windows proof, SDK Linux CI proof, and historical green jobs are distinct from the pending merge-readiness gates.
Remaining external release gates are official signing/publication approval, third-party license/SBOM/provenance review, dependency flow/merge of the matching SDK implementation, release-branch/backport decisions, runtime validation before advertising untested OS/architecture combinations, and an identified servicing owner for Playwright/Node/browser cadence. The package remains experimental and is emitted to Shipping only for acceptance/cross-repository validation.
Bundle the private cross-platform Playwright runtime from clean builds, allow launcher runtime roll-forward, and make startup cancellation and teardown reliably close owned browser resources.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Preserve framework-provided ComputeRunArguments host contracts, including quoted empty arguments, while keeping explicit browser host overrides. Replace raw page globals with the documented testingPlatformBrowser contract version 1 and launcher-private completion binding.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Keep browser URLs on the validated loopback origin, use the invoking SDK muxer, avoid Playwright payload copies in unit tests, coordinate package-owned host assets, and secure the launch-info handoff with private per-run directories and handle-based validation.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Add a one-shot, origin-validated fatal-error method to the versioned browser page contract so framework bootstrap and completion negotiation failures terminate the launcher immediately instead of waiting for the completion timeout.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Activate wrapping only for SDK-marked dotnet test invocations with HTTP bootstrap contract version 1, reject browser-inapplicable file and report options, and cover ordinary run, filtered/skipped/failing execution, and multi-target activation.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Require SDK invocation IDs for per-evaluation launcher configs, clean legacy and invocation-specific files, and link post-launch cancellation into the completion race and cleanup path.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Use the WebAssembly SDK and package-owned static host assets for the primary browser acceptance model, document the generated managed entry point and direct MTP HTTP transport, and recognize WasmAppHost App url readiness without matching debug URLs.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
A static module import is resolved before this supervisor body runs. If _framework/dotnet.js is missing or fails to load, neither complete nor reportFatalError is called, so the launcher waits for the full completion timeout (600 seconds by default) instead of reporting the bootstrap failure promptly. Load the module dynamically inside the guarded try and terminate through the versioned fatal-error API when bootstrap fails.
The reason will be displayed to describe this comment to others. Learn more.
Warning
Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.
Artifact transfer is enabled even when the peer omits its file-count limit, then the host invents a 10,000-file limit. That accepts a partially declared capability and can exceed the SDK's actual quota before failing mid-transfer. Require a positive FileArtifactTransferMaxFileCount alongside the other advertised limits.
Prevent duplicate artifact transfers from concurrent notifications
ConcurrentDictionary.GetOrAdd may run this async value factory more than once for the same path. Concurrent artifact notifications can therefore upload duplicate bytes, consume quota twice, and leave an orphan SDK artifact even though only one task is cached. Cache a Lazy<Task<string>> (or synchronize creation per path) so each path starts exactly one transfer.
Refresh validation evidence and CI status for the current pin
eng/browser-testing/sdk.json:3
The composed-validation pin has moved to df5a595…, while the PR description still claims validation against SDK 5b0e5fbe…, identifies b41d763f0 as the current TestFX head, and says final CI is green. The current PR head is 303a5d8c… and checks are still queued/in progress, so refresh the immutable evidence and CI statement after this exact pin/head completes validation.
Update protocol documentation for version 1.5 capabilities
Protocol 1.5 now implements HTTP reverse control and chunked artifact transfer, but the canonical docs/mstest-runner-protocol/004-protocol-dotnet-test-pipe.md still lists versions only through 1.4, documents serializer IDs only through 14, and calls browser reverse control future work. Update that protocol specification with the new capability keys, serializers, and fallback behavior in this PR.
A page can close without crashing or disconnecting Chromium (for example, via window.close()). That leaves both browserCompletion and WaitForExitAsync pending, so the run reports only after the completion timeout (10 minutes by default) instead of failing immediately. Subscribe to IPage.Close and complete _completion exceptionally, just as the crash handler does.
Update validation evidence for the current commit pairing
eng/browser-testing/sdk.json:3
The validation evidence in the PR description is for SDK commit 5b0e5fbe3a and TestFx head b41d763f0, but this pin is now df5a595… and the current PR head is 303a5d8…; the current composed browser run was still in progress when reviewed. Update the description with evidence for this exact pairing before retaining the “Final CI is green” claim.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The cross-repository protocol and process-lifecycle changes require human review, and artifact caching plus current-head validation evidence remain unresolved.
Update validation claims to match the current source and CI state
eng/browser-testing/sdk.json:3
The PR body’s validation claim no longer matches this pin or the current source state: it says the current head is b41d763f0, the aligned SDK is 5b0e5fbe3a, and final CI is green, but the actual head is 580258bd5a7d..., this file now selects 6868a2467c1f..., and the current Windows/Linux composed checks (build 1631986) are still in progress. The historical b6c7cac92/5b0e5fbe3a evidence therefore does not validate the source and counterpart selected by this revision. Please update the body after the current composed run completes (including current TestFx/SDK SHAs and accessible evidence), or explicitly label the existing results as historical and current-head validation as pending.
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
Unquoted SDK paths break launches from directories containing spaces, satellite assemblies are omitted from packaging, and a marker-file race can cause intermittent containment-test failures.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The pinned SDK uses incompatible wire IDs, disabling HTTP cancellation and artifact export, so the required acceptance cases cannot pass with this pairing.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The pinned SDK uses incompatible wire allocations, disabling managed HTTP cancellation and artifact export, so it must be updated and the composed suite rerun because earlier passing results predate the change.
Retain exact culture-path assertions and exercise the production MSBuild expression with relative and leading Unix/Windows metadata.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The pinned SDK uses incompatible wire allocations, disabling managed HTTP cancellation and dropping browser artifacts, so the SDK implementation and pin must be updated together and the composed suite rerun.
Pin the independently verified SDK f7edbfed while retaining immutable package source 11b0d39. Reuse the property-output parser for verbose metadata probes and cover explicit present/absent child settings. Record composed proof and both actual CI failure inventories without weakening product assertions.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Final test-triage resolution — Azure Pipelines build 1660099
Result: inconclusive. The build failed (check microsoft.testfx), but no actionable test failure could be identified.
The Linux Release job is failed in the pipeline timeline, but the collector found 0 failed/retried test results, 0 crash/hang diagnostics, 0 slow-test regressions and 0 timeline test signals.
Evidence is incomplete: 3 test-artifact downloads failed, so the test reports for some legs may be missing. I can't say the tests are clean.
History (previous 12 builds / 30 days) found no matching candidates, and it was not flagged as incomplete.
No issue was created because nothing meets the durable-issue thresholds.
Next step: inspect the failing Test step log of the "Linux Release" job in the build, and re-run the leg if the artifact publication failures were transient. Ordinary build failures are out of scope for this analysis (see Build Failure Analysis).
🤖 Automated content by GitHub Copilot. Generated by the Pipeline Test Triage workflow. · copilot · auto · 20.8 AIC · ⌖ 0.511 AIC · ⊞ 9.7K
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Warning
EXPERIMENT / PROTOTYPE ONLY — this pull request exists for design validation. It is not a shipping commitment, does not establish a supported package or API, and must not be interpreted as a product roadmap promise.
Pull request
Summary
This prototype adds an optional
Microsoft.Testing.Platform.Browserpackage that runs pure-managed browser-WASM MTP applications throughdotnet test, following dotnet/sdk#55906. It builds on the authenticated HTTP transport from #10143 and single-threaded browser/WASI TRX support from #10324 while keeping browser dependencies and servicing cadence out of core MTP.Current reconciled validation inputs (2026-11-02):
11b0d39f9079e5ead7b91ae5ab5161b5dcd8a147f7edbfedcb5319fd006078d1f9516f4a27442ddf, delivered by dotnet/sdk#5630563d157f265bff0abb1c5d5a5aeb3c32de9ecf083(SDK pin, test-harness parsing, and evidence; no shipping-source change)Current readiness: the fresh Windows stock composition passes all 11 required cases, and the source-matched SDK Linux CI now also passes 11/11. Runtime layouts are explicitly augmented with the producer-declared Core runtimes, not unmodified shipping SDKs. Current SDK Windows and TestFX reverse-direction Windows/Linux CI remain gates; the PR stays draft and Agent merge stays paused. Historical green runs below do not establish current-head readiness.
A project opts in with a
Microsoft.Testing.Platform.Browserpackage reference and an explicit Chromium-family executable. MTP remains authoritative for discovery, execution, filtering, progress/results, cancellation, and artifact production. The optional package owns browser/page/host lifecycle only; the browser app sends results and artifacts directly to the SDK HTTP gateway.Design and decision record
The maintained cross-repository design discussion is dotnet/sdk#55906. The implementation boundary is:
The maintained protocol decision and field reference records the current reconciliation: upstream coverage retains serializer 15, handshake property 20, and artifact metadata field 9; browser transfer uses serializers 17/18 and browser properties 26-31. Retired experimental serializer 16 and properties 21-25 are not reused. Mixed old/new peers do not activate mismatched decoders; absent transfer capability retains the warning/suppressed-VFS-path fallback.
The package uses Playwright's private stdio protocol and never opens an unauthenticated TCP DevTools endpoint. Bootstrap bearer data is expanded from the SDK-owned response file in memory and is not placed in URLs or logs.
xHarness was investigated but not reused at runtime. Its Selenium/WebDriver server, URL query arguments, DOM
tests_done, and console/result parsing conflict with direct MTP HTTP reporting. Its browser startup, container flags, retry, timeout, and cleanup experience informed this implementation.Protocol additions are capability-gated and backward compatible:
1.5.0handshake properties advertise HTTP control and artifact limits;BrowserTestingPackages.slnfis the conventional package-only build graph: eight package roots plus the non-packableMSTest.GlobalConfigsGeneratorbuild dependency. Acceptance is built separately at evaluatedNetCurrent. Package version lookups inAcceptanceTestBaseare lazy, so reduced feeds do not fail on unrelated absent packages; missing or duplicate packages still fail exactly when requested.CI uses existing capacity-backed public pools:
windows.vs2026preview.scout.amd64.open, required by the repo SDK's MSBuild 18.7 minimum and UWP package assets;build.ubuntu.2204.amd64.open, with the SDK-owned CI-onlyInstallBrowser.shprerequisite (fingerprint-verified Google signed APT repository when Chrome is absent).No system-tool/cache deletion or SDK component omission is used.
Demonstration
Canonical consumer shape:
The strict composed suite exercises normal run,
--list-tests, matching/zero/project filters, managed cancellation (exit3), intentional test failure aggregation, >1 MiB two-chunk artifact export and byte integrity, quota rejection, package/runtime layout, desktop non-interference, and process cleanup.Historical pre-reconciliation CI evidence from TestFX build 1632026, testing merge commit
f1c7147a236bb16641e85058956d91138a228f1fwith SDK66309ab55fce95ee42e5e2236c02f7371332dbf8(not proof of the current allocation):45287224, 11/11 passed, 0 failed/incomplete/not-applicable; Chrome155.0.8059.39; diagnostic artifact (2,075,499 bytes).45287840, 11/11 passed, 0 failed/incomplete/not-applicable; Edge153.0.4234.48; diagnostic artifact (2,147,863 bytes).Both downloaded TestFX artifacts pass the SDK-owned exact-11-case validator, record
succeeded=true, and record exit0for all six composed commands.Aligned SDK build 1632034 independently passed its browser jobs: Linux run
45287292and Windows run45287874, each 11/11 passed with zero failed/incomplete/not-applicable.These were four independent green composed jobs for the earlier inputs: TestFX Windows/Linux and SDK Windows/Linux. They are retained as history, not current Linux proof. No screenshot is included because these changes concern process/protocol and physical package contracts rather than rendered UI layout; exact commands, TRX outcomes, and artifact-integrity assertions are the clearer reproducible evidence.
Validation and regression proof
Current source-matched composition
From the SDK checkout at
f7edbfedcb5319fd006078d1f9516f4a27442ddf, with the restored counterpart's actual clean HEAD verified as11b0d39f9079e5ead7b91ae5ab5161b5dcd8a147:Result: parent exit
0; all seven recorded commands exit0; SDK product build, fresh TestFX shipping pack, and net12 acceptance-host build each have zero warnings/errors. Windows x64, SDK12.0.100-dev, Edge156.0.4314.58. All 11 exact names ineng/browser-testing/required-tests.jsonexecute and pass, zero skipped. The olderbtf-dd63a33ddirectory label is not used as source identity.The final
evidence.json,packages/manifest.json,runtime-manifest.json, andtest-results/browser.trxwere read independently. All eight staged package SHA-256 values and all 756 declared-runtime destination file hashes/lengths were independently rechecked after acceptance. Browser0.1.0-devSHA-256:73272744AC68618B59EAF8FA6283A8F9AB714DD5A9696F4E4B9D77691C88FAB8; MTP packages2.6.0-dev, MSTest packages4.6.0-dev.The layout is explicitly augmented: Core
8.0.32,9.0.21,10.0.13, and11.0.0-rc.2.26504.105come from the restored producer-declared private bootstrap. SDK/muxer/hostfxr, TFM, roll-forward, and exit/zero-result assertions are unchanged. This prerequisite is recorded asruntimeLayoutAugmented=true; it is not a claim that the shipping SDK contains every prior runtime.BrowserPackage_DotnetTestRunsAndListsTestsThroughSdkHttpGatewaypasses in the stock composition, including the large two-chunk artifact integrity assertions.BrowserPackage_SdkCancellationStopsManagedBrowserRunpasses;WindowsJob_CloseKillsWorkerAndSpawnedChildseparately passes with both process-exit assertions retained.BrowserPackage_ArtifactQuotaFailureFailsRunpasses; its intentionally nonzero child is not counted as an outer failure.BrowserPackage_ContainsPrivateCrossPlatformPlaywrightRuntime,BrowserPackage_PackNoBuildPreservesRuntimePayload, andBrowserPackage_PackWithoutBundledNodePreservesPrivateDriverAndLicensespass.SatellitePackagePath_NormalizesProductionMetadataseparately covers leading/relative Unix and Windows metadata.BrowserPackage_DesktopTestApplicationIsUnaffectedpasses with the declared runtime present;DotnetMuxer_ExplicitPathWithSpacesStartsSelectedExecutableseparately passes.The source-matched SDK Linux browser job in build 1659804 is now green. The coordinator independently reconciled actual log 91 and the downloaded
Browser_Linux_x64_Attempt1TRX/evidence: 11 distinct cases execute/pass, 0 failures/skips, all 11 recorded commands exit0, and all eight package-manifest sources are11b0d39f9079e5ead7b91ae5ab5161b5dcd8a147. The SDK tested merge ise6fff7ae1092ffff9b2ffb31626e75b5f157bd75, with verified parents SDKmain652269386d3c0702de4e6c9a6b8495e7eef5cfbcand SDK PR headf7edbfedcb5319fd006078d1f9516f4a27442ddf; the live SDK check also reports Success. Its explicit augmented Linux runtime manifest has 753 files, not the Windows layout's 756; Core 11 RC2libcoreclr.soSHA-256 isA5DD0CF3A4F6D36F13C3D71D3244B6457A2C510EEED7A616FC952CCFA8C28E80. SDK Windows remains in progress. This adds real counterpart Linux proof, not a TestFX current-caller CI pass.Current CI checkpoint and caller-only correction
The actual Windows and Linux TRX/evidence from TestFX build 1659780 were downloaded independently, rather than extrapolating one platform's results to the other. Both record tested merge
030bcf378c5fbbbed766f101ccb305498f1d110dand old SDK66309ab55fce95ee42e5e2236c02f7371332dbf8, not the final caller pin. Each executes 11 cases: 8 pass, 3 fail, 0 skip.On both platforms,
BrowserPackage_ContainsPrivateCrossPlatformPlaywrightRuntime,BrowserPackage_PackNoBuildPreservesRuntimePayload, andBrowserPackage_PackWithoutBundledNodePreservesPrivateDriverAndLicensespass. The three prior canonical-satellite/package-variant failures are absent in this actual Linux run, not merely predicted fixed from a Windows check.The remaining failures are exactly
BrowserPackage_DotnetTestRunsAndListsTestsThroughSdkHttpGateway(missing export directory),BrowserPackage_ArtifactQuotaFailureFailsRun(child exit0with the explicit unsupported-artifact-export warning), andBrowserPackage_DesktopTestApplicationIsUnaffected(Core11.0.0-rc.2.26504.105required but only 11 RC1 present; Linux exit150, Windows exit-2147450730). All five preceding build/evaluation commands exit0, while browser acceptance exits2. Published diagnostic artifacts: Linux and Windows.Ordinary Linux separately exposes four metadata-test failures because verbose CLI output prefixes the correct property with
Telemetry is: Disabled. The caller-only correction reuses the already-tested last-nonempty-line parser, preserves exacttools/net8.0/any/tr/equality, and explicitly arranges the child setting both present and absent. It does not disable CI tracing, relax any satellite/exit assertions, change wire fields, or alter shipping source.The same eight
SatellitePackagePath_NormalizesProductionMetadatarows execute in the local harness comparison: before extraction correction, four verbose rows fail at the intended banner-versus-path assertion and four absent-setting rows pass (exit2); afterward 8/8 pass, zero skips, exit0. This is a test-harness reproduction, not additional production-mutation proof. Both builds below finish with 0 warnings/errors, exit0, using the CMD-local Windows PowerShell bootstrap path. The exact metadata selector is unchanged:The same eight rows also pass 8/8, zero skips, exit
0with the parent process explicitly inheriting the CI-style verbose setting, proving that child absence is not accidentally inherited:That override is confined to the task-owned PowerShell process; no user-global setting changes.
The retained two-case selector also executes/passes 2/2, zero skips, exit
0:The production files remain byte-for-byte unchanged from the SDK's immutable package-source
11b0d39f9079e5ead7b91ae5ab5161b5dcd8a147. The corrected caller and test harness do not require cycling the SDK's package-source pin. Final TestFX current-head Windows/Linux and SDK Windows CI still gate readiness; the old-pin failures above are not silently reclassified as passing.Test-value evidence
c22e5fd7source restored onlyServerControlTransportfrom 26 to 20, retaining the four new cases/assertions. It compiled cleanly and executed four cases: three intended control-capability assertion failures, one pass, zero skips, exit2. The aligned four-case selection passes 4/4. The nested harness changed only precedence between byte-equivalent global analyzer policies; no checks were suppressed.1rather than0. With the fixes and fresh packages, the covering six-case selection passes 6/6, zero skips.1659688exposedtools/net8.0/any//<culture>/...; its exact package assertions were retained. At thedd63a33dproduction expression, four metadata cases execute: the two leading-separator cases fail onany//tr/, and two relative cases pass. The normalized11b0d39fexpression passes all four; the covering package/path selection passes 10/10. These are production-expression checks on Windows, not substituted Linux-runtime proof.StartServerControlChannelAsync_SupportedButPipeNameEmptyDoesNotCreateListenercase executes/fails before the production allocation guard and executes/passes afterward with the same assertion. PID-marker publication now closes its temporary file before renaming; its real Windows containment case passes without weakening lifetime assertions. No deterministic timing-failure claim is made for that race.The TestFX current-caller Windows/Linux jobs remain readiness gates. Build
1659688also has a separately retained ordinary Linux ReleaseMSB3026shared test-layout copy failure. Its project source is unchanged, but graph/global-input changes can affect exposure; concurrent writers and PR causation are unproven. The failed-binlog/log endpoints subsequently return 404. No workaround was added, and a later passing run alone is not described as fixing that collision.Historical focused repository validation
build.cmd -c Release -pack -projects BrowserTestingPackages.slnf -mt 0 -bl -bln BrowserTestingPackages-fresh.binlogfrom a new detached checkout atbbbbfd23d4de8ed70a261b52a326804492b4b037: passed, exit0, 0 warnings/errors. Exactly eight non-symbol shipping nupkgs were produced and every nuspec repository commit matched that exact source SHA.build.cmd -c Release -projects test\IntegrationTests\Microsoft.Testing.Platform.Acceptance.IntegrationTests\Microsoft.Testing.Platform.Acceptance.IntegrationTests.csproj -mt 0 -bl -bln AcceptanceTestBaseLazy-final.binlog: passed, exit0, 0 warnings/errors.AcceptanceTestBaseTests: 1/1 passed, 0 skipped. It proves unused absent packages are not resolved, required absent packages fail withfound 0, and duplicate packages fail withfound 2.BrowserPackage_ContainsPrivateCrossPlatformPlaywrightRuntimewhile Shipping contained exactly the required eight dev nupkgs: 1/1 passed, 0 skipped; the original 43-package local feed was restored afterward.BuildDriverTests: 2/2 passed, covering nonzerobuild.cmdfailure propagation/binlog creation and root-wrapper forwarding of-mt 0.1632026: Linux 11/11, Windows 11/11, no skips.1632034: Linux 11/11, Windows 11/11, no skips.The required-test manifest contains 11 exact TRX names and the shared validator requires every name exactly once, all Passed, zero skipped, and a valid TRX. Every generated fixture uses a unique short NuGet cache and compares all eight restored
project.assets.jsonSHA-512 values with the staged nupkg bytes.Immutable aligned package evidence remains at source
b6c7cac92f7eeb788ae026471239ff110207bc24underartifacts/validation/Microsoft.Testing.Platform.Browser/b6c7cac92-aligned/Shipping; the Browser nupkg SHA-256 is2D078CB340E45A0E6C1CC5894BFF3148E29218683F36D5D038F24B3C78E67580.At this body update, SDK Linux success is confirmed above; SDK Windows and TestFX reverse-direction/current-caller CI have not been claimed green. The PR remains draft and TestFX app maintenance remains paused. The source-matched local Windows proof, SDK Linux CI proof, and historical green jobs are distinct from the pending merge-readiness gates.
Remaining external release gates are official signing/publication approval, third-party license/SBOM/provenance review, dependency flow/merge of the matching SDK implementation, release-branch/backport decisions, runtime validation before advertising untested OS/architecture combinations, and an identified servicing owner for Playwright/Node/browser cadence. The package remains experimental and is emitted to Shipping only for acceptance/cross-repository validation.