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.
on this pageshowhide
explore
- Division of Work14 questions
- Worker Lifetime5 questions
- Parallel and Serial Modes5 questions
- Shard Splitting4 questions
- Failure Controls9 questions
- Retry Attempts4 questions
- Fail-Fast Limits5 questions
- Pipeline Handoff10 questions
- Built-In Reporters5 questions
- Container Images and CI5 questions
questions
page 2 of 2Playwright discards a worker process after any test failure - what does that guarantee cost a large suite?
basics
~20 sIt 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.
In Playwright, why can a few test.describe.serial groups dominate a large suite's wall-clock?
basics
~20 sA 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.
In Playwright, which `Reporter` hooks does a custom reporter implement to record every test's outcome?
basics
~10 sA 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.
showing 31–33 of 33