Max number of test files running at the same time (default: CPU cores)
Use worker threads to run tests (enabled by default). If `false`, tests will run in child processes
If `false`, does not fail a test if it doesn't run assertions
environment variables
Specifies environment variables to be made available to the tests. The environment variables defined here override the ones from `process.env`
matchN(>=1, [#."array-of-strings", {
{
[=~"^(c|m)?js$"]: true
}
{
[!~"^(c|m)?js$" & !~"^()$"]: "commonjs" | "module"
}
}])Extensions of test files. Setting this overrides the default `["cjs", "mjs", "js"]` value, so make sure to include those extensions in the list. Experimentally you can configure how files are loaded
Timeouts in AVA behave differently than in other test frameworks. AVA resets a timer after each test, forcing tests to quit if no new test results were received within the specified timeout. This can be used to handle stalled tests. See our timeout documentation for more options
If `false`, disable parallel builds (default: `true`)
configuration
Configures @ava/typescript for projects that precompile TypeScript. Alternatively, you can use `ts-node` to do live testing without transpiling, in which case you shouldn't use the `typescript` property
paths
AVA searches your entire project for `*.js`, `*.cjs`, `*.mjs` and `*.ts` files (or other extensions you've configured). It will ignore such files found in the `rewritePaths` targets (e.g. `build/`). If you use more specific paths, for instance `build/main/`, you may need to change AVA's `files` configuration to ignore other directories. Paths are relative to your project directory
AVA Config Schema
Configuration Schema for the JavaScript test runner AVA