Skip to content

fix: enforce bounded parallel test execution #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
glennmichael123 merged 2 commits into from
Sep 29, 2026
Merged

fix: enforce bounded parallel test execution #21

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ae2754f
fix: bound parallel execution to configured workers
glennmichael123 Sep 29, 2026
5ad9913
docs: define parallel hook and reporting semantics
glennmichael123 Sep 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,6 +146,25 @@ The accepted top-level sections are `test`, `parallel`, `reporter`, `snapshot`,
`watch`, `memory`, `ui`, and `coverage`. Options retain the same execution-mode
limitations as their CLI equivalents; unsupported combinations fail explicitly.

### Parallel execution semantics

Programmatic runners can enable bounded execution with `RunnerOptions.parallel`
and set `n_jobs`. A configured value is the exact maximum number of active test
workers; omitting it uses the host's logical CPU count, with a one-worker
fallback when detection is unavailable.

Suites and nested suites are visited in declaration order. `beforeAll` and
`afterAll` run once on the coordinating thread around that suite and its nested
suites. Direct tests within a suite may overlap. Their inherited `beforeEach`
and `afterEach` hooks run on the same worker as the test, so per-test hook order
is preserved but hooks from different tests may overlap. Hook state and the
allocator passed to tests must therefore be thread-safe.

Reporter callbacks never run concurrently: test results are emitted in
declaration order after each parallel batch, making output and final totals
deterministic. A parallel batch is already scheduled as a unit, so `bail` cannot
cancel tests that have started.

### Programmatic Mode

For more control, you can manually register tests:
Expand Down
Loading
Loading