Add Web Platform Test runner infrastructure - #617
Closed
andrewiggins wants to merge 17 commits into
Closed
Conversation
andrewiggins
marked this pull request as ready for review
July 16, 2026 03:03
andrewiggins
force-pushed
the
wpt-runner-infrastructure
branch
from
August 20, 2026 21:14
ce419ac to
4da2468
Compare
Contributor
Author
|
Superseded by the three-PR replacement stack:
The replacement stack gives each PR a self-contained executable outcome. This PR is closed without merging. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
@remote-dom/wpt-runnerworkspace package for running selected upstreamtestharness.jsHTML files against@remote-dom/polyfillwithout modifying the upstream filesWindow, private result transport, and worker-specific network restrictionsArchitecture
The browser control page parses each selected WPT file and turns supported top-level markup and classic scripts into generated source in their original order. The CLI reuses one control page across files, but each file runs in a fresh module worker with a new
Windowfrom@remote-dom/polyfill.Runner results travel over a private
MessagePortrather than the worker's public message channel. A worker-specific Content Security Policy blocks network connections and nested workers while allowing the same-origin module loading and generated-code execution required by the runner. Served WPT files use ETag revalidation to avoid repeatedly transferring shared resources such astestharness.js.This infrastructure tests the worker-side DOM implementation directly. It intentionally does not construct a Remote DOM host receiver or claim transport and rendering behavior. The initial capability table contains only the runner smoke fixture. Follow-up PRs can add upstream DOM, HTML, and SVG files one capability at a time.
Validation
pnpm run lintpnpm run type-checkpnpm exec vitest runpnpm run test:wptWPT_ROOT=/path/to/wptreuses a local checkout without downloadingChangeset
An empty changeset is included because
@remote-dom/wpt-runneris private test infrastructure and does not release a public package.