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

feat: support describe.sequential #3771

Merged
merged 3 commits into from
Jul 19, 2023
Merged

feat: support describe.sequential #3771

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d8bb1a4
feat: support `describe.sequential`
fenghan34 Jul 14, 2023
439e193
docs: update
fenghan34 Jul 15, 2023
1d76de9
fix: grammar
fenghan34 Jul 16, 2023
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
Prev Previous commit
fix: grammar 
Co-authored-by: Anjorin Damilare <damilareanjorin1@gmail.com>
  • Loading branch information
@fenghan34 @dammy001
fenghan34 and dammy001 authored Jul 16, 2023
commit 1d76de92e81cd423b7770cef4925da29c4061a60
2 changes: 1 addition & 1 deletion docs/api/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -643,7 +643,7 @@ You cannot use this syntax, when using Vitest as [type checker](/guide/testing-t

- **Type:** `(name: string | Function, fn: TestFunction, options?: number | TestOptions) => void`

`describe.sequential` in a suite marks every tests as sequential. This is useful if you want to run tests in sequential within `describe.concurrent` or with the `--sequence.concurrent` command option.
`describe.sequential` in a suite marks every test as sequential. This is useful if you want to run tests in sequential within `describe.concurrent` or with the `--sequence.concurrent` command option.

```ts
describe.concurrent('suite', () => {
Expand Down