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
Set`concurrent`to`false`tooptoutofconcurrencyinheritedfrom [`describe.concurrent`](/api/describe#describe-concurrent) or [`sequence.concurrent`](/config/sequence#sequence-concurrent):
221
221
222
-
-**Type:**`boolean`
223
-
-**Default:**`true`
224
-
-**Alias:** [`test.sequential`](#test-sequential)
225
-
226
-
::: warningDEPRECATED
227
-
Use [`concurrent: false`](#concurrent) insteadwhenyouneedtooverrideinheritedorconfiguredconcurrency.
Use [`concurrent: false`](#concurrent) instead when you need to override inherited or configured concurrency.
466
-
:::
467
-
468
-
`test.sequential` marks a test as sequential. This is useful if you want to run tests in sequence within `describe.concurrent` or with the `--sequence.concurrent` command option.
Copy file name to clipboardExpand all lines: docs/guide/migration.md
+10-31Lines changed: 10 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,48 +13,27 @@ outline: deep
13
13
Vitest 5.0 is currently in beta. This section tracks breaking changes as they are merged and may change before the stable release.
14
14
:::
15
15
16
-
### String Values in `$` Test Titles Are No Longer Quoted
16
+
### Removed `test.sequential`, `describe.sequential`, and `sequential` Options
17
17
18
-
When interpolating string values in `test.each`, `test.for`, `describe.each`, or `describe.for` titles with the `$` syntax, Vitest no longer wraps those string values in quotes.
19
-
20
-
This affects generated task names in reporter output, snapshots, and any tooling that matches tests by their generated title.
18
+
Vitest 5.0 removes the deprecated `test.sequential`, `describe.sequential`, and `sequential` test options. Use `concurrent: false` when you need a test or suite to opt out of inherited or globally configured concurrency.
21
19
22
20
```ts
23
-
test.for([{ name: 'Alice' }])('I am $name', () => {})
### `chaiConfig.truncateThreshold` No Longer Controls Test Title Value Truncation
36
-
37
-
Vitest now formats interpolated task title values with its display formatter based on `@vitest/pretty-format`, instead of Chai/loupe formatting.
38
-
39
-
Most output should stay similar, but generated titles or assertion output involving formatted values may have small formatting differences.
40
-
41
-
If you used `chaiConfig.truncateThreshold` to control truncation in `test.each`, `test.for`, `describe.each`, or `describe.for` titles, use `taskTitleValueFormatTruncate` instead:
If you want *all* tests in your project to run concurrently by default, set [`sequence.concurrent`](/config/sequence#sequence-concurrent) to `true` in your config.
82
82
83
+
You can opt individual tests or suites out of inherited concurrency with `concurrent: false`:
When tests run concurrently, lifecycle hooks behave differently. `beforeAll` and `afterAll` still run once for the group, but `beforeEach` and `afterEach` run for each test — potentially at the same time, since the tests themselves overlap.
0 commit comments