+1 -1

docs/advanced/pool.md

Reviewed

··· 1 1 # Custom Pool 2 2 3 3 ::: warning 4 4 - This is advanced API. If you are just running tests, you probably don't need this. It is primarily used by library authors. 4 4 + This is advanced API. If you just want to [run tests](/guide/), you probably don't need this. It is primarily used by library authors. 5 5 ::: 6 6 7 7 Vitest runs tests in pools. By default, there are several pools:

+1 -1

docs/advanced/runner.md

Reviewed

··· 1 1 # Test Runner 2 2 3 3 ::: warning 4 4 - This is advanced API. If you are just running tests, you probably don't need this. It is primarily used by library authors. 4 4 + This is advanced API. If you just want to [run tests](/guide/), you probably don't need this. It is primarily used by library authors. 5 5 ::: 6 6 7 7 You can specify a path to your test runner with the `runner` option in your configuration file. This file should have a default export with a class constructor implementing these methods:

+5 -1

docs/guide/in-source.md

Reviewed

··· 4 4 5 5 # In-Source Testing 6 6 7 7 - Vitest also provides a way to run tests within your source code along side the implementation, similar to [Rust's module tests](https://doc.rust-lang.org/book/ch11-03-test-organization.html#the-tests-module-and-cfgtest). 7 7 + Vitest provides a way to run tests within your source code along side the implementation, similar to [Rust's module tests](https://doc.rust-lang.org/book/ch11-03-test-organization.html#the-tests-module-and-cfgtest). 8 8 9 9 This makes the tests share the same closure as the implementations and able to test against private states without exporting. Meanwhile, it also brings a closer feedback loop for development. 10 10 + 11 11 + ::: warning 12 12 + This guide explains how to write tests inside your source code. If you need to write tests in separate test files, follow the ["Writing Tests" guide](/guide/#writing-tests). 13 13 + ::: 10 14 11 15 ## Setup 12 16