You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should all test files run in parallel. Setting this to `false` will override `maxWorkers`and `minWorkers` options to `1`.
972
+
Should all test files run in parallel. Setting this to `false` will override `maxWorkers`option to `1`.
1001
973
1002
974
::: tip
1003
975
This option doesn't affect tests running in the same file. If you want to run those in parallel, use `concurrent` option on [describe](/api/#describe-concurrent) or via [a config](#sequence-concurrent).
@@ -1009,12 +981,6 @@ This option doesn't affect tests running in the same file. If you want to run th
1009
981
1010
982
Maximum number or percentage of workers to run tests in. `poolOptions.{threads,vmThreads}.maxThreads`/`poolOptions.forks.maxForks` has higher priority.
1011
983
1012
-
### minWorkers<NonProjectOption /> {#minworkers}
1013
-
1014
-
-**Type:**`number | string`
1015
-
1016
-
Minimum number or percentage of workers to run tests in. `poolOptions.{threads,vmThreads}.minThreads`/`poolOptions.forks.minForks` has higher priority.
- Reporter APIs `onCollected`, `onSpecsCollected`, `onPathsCollected`, `onTaskUpdate` and `onFinished`. See [`Reporters API`](/advanced/api/reporters) for new alternatives. These APIs were introduced in Vitest `v3.0.0`.
239
239
-`deps.external`, `deps.inline`, `deps.fallbackCJS` config options. Use `server.deps.external`, `server.deps.inline`, or `server.deps.fallbackCJS` instead.
240
240
-`browser.testerScripts` config option. Use [`browser.testerHtmlPath`](/guide/browser/config#browser-testerhtmlpath) instead.
241
+
-`minWorkers` config option. Only `maxWorkers` has any effect on how tests are running, so we are removing this public option.
241
242
242
243
This release also removes all deprecated types. This finally fixes an issue where Vitest accidentally pulled in `@types/node` (see [#5481](https://github.com/vitest-dev/vitest/issues/5481) and [#6141](https://github.com/vitest-dev/vitest/issues/6141)).
Copy file name to clipboardExpand all lines: docs/guide/parallelism.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ By default, Vitest runs _test files_ in parallel. Depending on the specified `po
12
12
-`forks` (the default) and `vmForks` run tests in different [child processes](https://nodejs.org/api/child_process.html)
13
13
-`threads` and `vmThreads` run tests in different [worker threads](https://nodejs.org/api/worker_threads.html)
14
14
15
-
Both "child processes" and "worker threads" are refered to as "workers". You can configure the number of running workers with [`minWorkers`](/config/#minworkers) and [`maxWorkers`](/config/#maxworkers)options. Or more granually with [`poolOptions`](/config/#pooloptions) configuration.
15
+
Both "child processes" and "worker threads" are refered to as "workers". You can configure the number of running workers with [`maxWorkers`](/config/#maxworkers)option. Or more granually with [`poolOptions`](/config/#pooloptions) configuration.
16
16
17
17
If you have a lot of tests, it is usually faster to run them in parallel, but it also depends on the project, the environment and [isolation](/config/#isolate) state. To disable file parallelisation, you can set [`fileParallelism`](/config/#fileparallelism) to `false`. To learn more about possible performance improvements, read the [Performance Guide](/guide/improving-performance).
0 commit comments