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
Multiple async describe causes some test to not be run. #703
Comments
Is this supported by Jest? I only see one closed merge request in Jest saying that they will not support it. You can use async |
Agree, describe should not be async. |
@Demivan, it makes sense. In this case, shouldn't the type vitest/packages/vitest/src/types/tasks.ts Line 81 in 735e507
be changed to not accept asynchronous functions? |
Describe the bug
The bug is quite strange, when using multiple nested async describe, some test can be skipped for no apparent reason.
As pointed out in the repro comments, commenting some describes make the previously skipped test to run.
There is no part of the form to do it, so, thank you guys a lot, that is amazing work you are doing here! 🚀
Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-trh7ej?file=test/suite.test.ts
I isolated a minimal repro with only three describe and an async function using a timeout.
System Info
Used Package Manager
npm
Validations
The text was updated successfully, but these errors were encountered: