@@ -350,11 +350,12 @@ in the [test runner execution model][] section.
350
350
351
351
### Test runner execution model
352
352
353
- Each matching test file is executed in a separate child process. If the child
354
- process finishes with an exit code of 0, the test is considered passing.
355
- Otherwise, the test is considered to be a failure. Test files must be
356
- executable by Node.js, but are not required to use the ` node:test ` module
357
- internally.
353
+ Each matching test file is executed in a separate child process. The maximum
354
+ number of child processes running at any time is controlled by the
355
+ [ ` --test-concurrency ` ] [ ] flag. If the child process finishes with an exit code
356
+ of 0, the test is considered passing. Otherwise, the test is considered to be a
357
+ failure. Test files must be executable by Node.js, but are not required to use
358
+ the ` node:test ` module internally.
358
359
359
360
Each test file is executed as if it was a regular script. That is, if the test
360
361
file itself uses ` node:test ` to define tests, all of those tests will be
@@ -2551,6 +2552,7 @@ added:
2551
2552
[ TTY ] : tty.md
2552
2553
[ `--experimental-test-coverage` ] : cli.md#--experimental-test-coverage
2553
2554
[ `--import` ] : cli.md#--importmodule
2555
+ [ `--test-concurrency` ] : cli.md#--test-concurrency
2554
2556
[ `--test-name-pattern` ] : cli.md#--test-name-pattern
2555
2557
[ `--test-only` ] : cli.md#--test-only
2556
2558
[ `--test-reporter-destination` ] : cli.md#--test-reporter-destination
0 commit comments