-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
Vitest conventions #11
Labels
test
Adding missing tests or correcting existing tests
Comments
Perhaps move this to a discussion instead |
It also has ... which is what I prefer to use. describe('description...', () => {
for (const [a, b] of TESTS) {
it.concurrent( ... )
}
} https://vitest.dev/api/#test-concurrent Additionally, can mark the entire inner |
kalisjoshua
added a commit
that referenced
this issue
Nov 20, 2024
additionally clean up folder names for fixtures. issue #11
7 tasks
7 tasks
kalisjoshua
added a commit
that referenced
this issue
Nov 22, 2024
7 tasks
7 tasks
kalisjoshua
added a commit
that referenced
this issue
Dec 2, 2024
kalisjoshua
added a commit
that referenced
this issue
Dec 3, 2024
kalisjoshua
added a commit
that referenced
this issue
Dec 3, 2024
kalisjoshua
added a commit
that referenced
this issue
Dec 3, 2024
kalisjoshua
added a commit
that referenced
this issue
Dec 4, 2024
kalisjoshua
added a commit
that referenced
this issue
Dec 18, 2024
kalisjoshua
added a commit
that referenced
this issue
Dec 18, 2024
kalisjoshua
added a commit
that referenced
this issue
Dec 18, 2024
kalisjoshua
added a commit
that referenced
this issue
Dec 18, 2024
brandonjpierce
pushed a commit
that referenced
this issue
Dec 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A common pattern we have is doing something like:
However, vitest does have
it.each
which works on pairs like datasets. Should we switch to that method instead?The text was updated successfully, but these errors were encountered: