···230230})
231231```
232232233233-## describe.sequential
233233+## describe.sequential <Deprecated /> {#describe-sequential}
234234235235- **Alias:** `suite.sequential`
236236+237237+::: warning DEPRECATED
238238+Use [`concurrent: false`](/api/test#concurrent) instead when you need to override inherited or configured concurrency.
239239+:::
236240237241`describe.sequential` in a suite marks every test as sequential. This is useful if you want to run tests in sequence within `describe.concurrent` or with the `--sequence.concurrent` command option.
238242
+9-1
docs/api/test.md
···223223- **Default:** `true`
224224- **Alias:** [`test.sequential`](#test-sequential)
225225226226+::: warning DEPRECATED
227227+Use [`concurrent: false`](#concurrent) instead when you need to override inherited or configured concurrency.
228228+:::
229229+226230Whether tests run sequentially. When both `concurrent` and `sequential` are specified, `concurrent` takes precedence.
227231228232### skip
···453457454458Note that if tests are synchronous, Vitest will still run them sequentially.
455459456456-## test.sequential
460460+## test.sequential <Deprecated /> {#test-sequential}
457461458462- **Alias:** `it.sequential`
463463+464464+::: warning DEPRECATED
465465+Use [`concurrent: false`](#concurrent) instead when you need to override inherited or configured concurrency.
466466+:::
459467460468`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.
461469