Expand description
The browser tests a measured server answered: what the browser runner reported for each attempt, which a Python or Ruby server’s run takes its tests from, and the rule that gives a request naming no test to one.
Structs§
- InProcess
- The suite’s own test attempts, in the order each process ran them: what a request to a server the suite runs in its own process – a live server a browser or the test itself calls – is judged by. A process writes its records in order, so the attempt whose phase began last before the request did is the one running when it came: exactly, where the attempts were run one after another, and no one’s where they interleave.
- Served
Test - A browser test whose requests a measured server answered: what the browser runner reported for it, which no runner of the server’s language saw.
Constants§
- REQUEST_
WORKER - The worker a server’s runtime records a request that names no test under, numbered within its process.
Functions§
- owner
- The attempt a request that named no test belongs to: the one running when it came, if only one was, among the attempts its process answered a request of where it answered any – with a server per worker, the worker’s test, whatever other workers ran meanwhile – and among every attempt otherwise.
- read
- Each browser test attempt the suite reported, read from the Playwright fixture’s evidence lines.
- read_
attempts - Each test attempt any runner reported – node:test, Vitest, Jest, Mocha, AVA, tap, Playwright – read from the evidence journals they all write.
Type Aliases§
- Attempt
- A test attempt: worker, test, retry.
- Phase
Start - One phase starting: in which process (its transport), where in its records, and of which attempt (worker, test, retry).