-
-
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
testNamePattern runs beforeAll/afterAll in excluded suites #4820
Comments
Hi! Thanks for reporting, I'm also able to reproduce it |
Seems like a duplicate of #4487 right? |
cc: @aaronabramov |
@rogeliog @aaronabramov |
I think @aaronabramov would know better than me 😃 |
i think this is the way jasmine runs tests. I think it was fixed in Jasmine at some point, but we're still using the old/custom version of it. |
@aaronabramov #4166 (comment) says you are working on |
@timjacobi unfortunately jest-circus is not the priority right now :( |
This seems to be the PR that fixed it in the Jasmine side, jasmine/jasmine#1225 |
My issue (#5593) was closed as a duplicate of this one, but I think mine captures several test cases that are not covered here, so I'll link to the repl.it repro in case it's helpful. |
Any news on this issue ? |
We tried to port the fix from Jasmine in #5051, but it didn't work. Help very much welcome! |
Fixed in #6234 |
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. |
Given a test file with the following contents:
running
jest -t abc
runs thebeforeAll
callback in thedef
suite. The failure is reported underdef › does not run def
(though the summary at the bottom says "1 skipped, 1 passed, 2 total")I would have expected the beforeAll function not to have run.
felipeochoa/jest-bug-demo is a basic repro repo.
Tested on jest 21.2.1, node 8.9.0, and yarn 1.0.1
The text was updated successfully, but these errors were encountered: