-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Parity in concurrent between jasmine and jest-jasmine #9163
Comments
Does it work just making the test |
Yes, making it |
I'll raise a PR for this, if this is supposed to be the expected behavior |
Yeah, no reason not to. I think the point is that, since js is js, if your tests isn't async marking it concurrent makes no sense. Not sure what we should do about the |
This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
🐛 Bug Report
There seems to be a parity between
jest-jasmine
andjest-circus
on dealing withtest.concurrent
For the below example
jest-jasmine
throwswhereas
jest-circus
passesThe examples I've found for
test.concurrent
mention that the test should return a Promise#4281 (comment)
To Reproduce
Expected behavior
Consistent behavior between
jest-jasmine
andjest-circus
envinfo
System: OS: macOS Mojave 10.14.6 CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz Binaries: Node: 10.16.0 Yarn: 1.13.0 npm: 6.9.0 npmPackages: jest: ^24.9.0 => 24.9.0
cc \ @SimenB Noticed this while I was working on #8985
The text was updated successfully, but these errors were encountered: