run
Documentation / @wtf/project-wpt / run
A test file of the WPT, run: runTest, in a realm the caller gives, whose globals are the
built-ins of ./builtins and what the caller maps in, nothing of the process’s own global, with
testharness.js hooked so each subtest is a result. Nothing here imports Node: the realm (in Node,
a node:vm context), the timers and the clock of the platform, and what hears a rejection no one
handles are parameters.
The context has, in this order, each over the one before: the language’s built-ins of its own
realm; the intrinsics of this realm, of which an implementation’s errors and buffers are;
the WinterTC builtins; the host of the harness — self, the context’s global, location,
the file’s address, GLOBAL, which says it is no window, worker or shadow realm, the timers,
which are the platform’s and which the run clears when the file ends, and addEventListener, by which the harness hears an
error no script catches and a rejection no one handles; and the globals of the caller, each of its names, an
undefined taking one out. Then it evaluates testharness.js, hooks its results, and evaluates
the file’s // META: script= scripts and the file, one after another, at once: the harness
starts the tests once they are all evaluated, and ends as the last ends, or as the file’s time
runs out, its subtests not done then a TIMEOUT.