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
Copy file name to clipboardExpand all lines: docs/config/index.md
+52Lines changed: 52 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -772,6 +772,58 @@ Please, be aware of these issues when using this option. Vitest team cannot fix
772
772
773
773
Similar as `vmThreads` pool but uses `child_process` instead of `worker_threads` via [tinypool](https://github.com/tinylibs/tinypool). Communication between tests and the main process is not as fast as with `vmThreads` pool. Process related APIs such as `process.chdir()` are available in `vmForks` pool. Please be aware that this pool has the same pitfalls listed in `vmThreads`.
The pool group order in which this project runs its tests. If not specified, all projects run in parallel.
781
+
782
+
This option only works if you have more than one project in your [workspace](/guide/workspace). If the same value is used in different projects, all those project will run together.
* The pool group order in which this project runs its tests.
354
+
* If not specified, all projects run in parallel.
355
+
*
356
+
* You can group tests in certain projects to run together and delay others.
357
+
*
358
+
* @default 0
359
+
*/
360
+
poolOrder?: number
361
+
352
362
/**
353
363
* Maximum number or percentage of workers to run tests in. `poolOptions.{threads,vmThreads}.maxThreads`/`poolOptions.forks.maxForks` has higher priority.
0 commit comments