mirror of
https://github.com/vitest-dev/vitest.git
synced 2025-12-08 18:26:03 +00:00
44 lines
1.4 KiB
Markdown
44 lines
1.4 KiB
Markdown
---
|
|
title: expect | Config
|
|
outline: deep
|
|
---
|
|
|
|
# expect
|
|
|
|
- **Type:** `ExpectOptions`
|
|
|
|
## expect.requireAssertions
|
|
|
|
- **Type:** `boolean`
|
|
- **Default:** `false`
|
|
|
|
The same as calling [`expect.hasAssertions()`](/api/expect#expect-hasassertions) at the start of every test. This makes sure that no test will pass accidentally.
|
|
|
|
::: tip
|
|
This only works with Vitest's `expect`. If you use `assert` or `.should` assertions, they will not count, and your test will fail due to the lack of expect assertions.
|
|
|
|
You can change the value of this by calling `vi.setConfig({ expect: { requireAssertions: false } })`. The config will be applied to every subsequent `expect` call until the `vi.resetConfig` is called manually.
|
|
:::
|
|
|
|
::: warning
|
|
When you run tests with `sequence.concurrent` and `expect.requireAssertions` set to `true`, you should use [local expect](/guide/test-context.html#expect) instead of the global one. Otherwise, this may cause false negatives in [some situations (#8469)](https://github.com/vitest-dev/vitest/issues/8469).
|
|
:::
|
|
|
|
## expect.poll
|
|
|
|
Global configuration options for [`expect.poll`](/api/expect#poll). These are the same options you can pass down to `expect.poll(condition, options)`.
|
|
|
|
### expect.poll.interval
|
|
|
|
- **Type:** `number`
|
|
- **Default:** `50`
|
|
|
|
Polling interval in milliseconds
|
|
|
|
### expect.poll.timeout
|
|
|
|
- **Type:** `number`
|
|
- **Default:** `1000`
|
|
|
|
Polling timeout in milliseconds
|