skip to content

Run Orchestration

How a whole suite is run: the options and flags that split work across worker processes, react to failures, and hand results to CI. Asked because this is where suites break at scale.

part ofPlaywrightread it →
on this pageshow

explore

questions

page 2 of 2

Playwright discards a worker process after any test failure - what does that guarantee cost a large suite?

level: principalimportance: should knowfreq 30%

basics

~20 s

It buys certainty that no test inherits a process a failure left dirty. It costs a cold browser launch plus per-worker set-up for every failure, so a red payroll run is measurably slower than a green one.

open as a page

In Playwright, why can a few test.describe.serial groups dominate a large suite's wall-clock?

level: seniorimportance: nice to knowfreq 32%

basics

~20 s

A serial group is indivisible: its tests run in order on one worker, so its total duration is a floor no extra parallelism can cut. Retries replay the whole group, so the longest chain sets the finish time.

open as a page

In Playwright, which `Reporter` hooks does a custom reporter implement to record every test's outcome?

level: seniorimportance: nice to knowfreq 32%

basics

~10 s

A class implementing Reporter from @playwright/test/reporter, wired through the reporter option. onBegin starts the run, onTestBegin and onTestEnd bracket each attempt, onStepBegin and onStepEnd cover steps, and onEnd then onExit close the run.

open as a page

showing 31–33 of 33