Skip to content
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

Link to CLI options to clarify how to run tests in separate processes #3345

Merged
merged 2 commits into from
Oct 27, 2024
Merged

Link to CLI options to clarify how to run tests in separate processes #3345

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b71dac6
Update 01-writing-tests.md
thoughtsunificator Oct 26, 2024
44e48b7
Relative link
novemberborn Oct 27, 2024
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
2 changes: 1 addition & 1 deletion docs/01-writing-tests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ AVA tries to run test files with their current working directory set to the dire

## Test isolation

By default each test file is run in a new worker thread. You can fall back running in separate processes.
By default each test file is run in a new worker thread. You can fall back running in separate processes (see `workerThreads` [CLI option](./06-configuration.md#options)).

AVA will set `process.env.NODE_ENV` to `test`, unless the `NODE_ENV` environment variable has been set. This is useful if the code you're testing has test defaults (for example when picking what database to connect to). It may cause your code or its dependencies to behave differently though. Note that `'NODE_ENV' in process.env` will always be `true`.

Expand Down