-
-
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
TypeError: Cannot read property 'result' of undefined at isAfterAll when I comment out all "it" blocks #5531
Comments
because we can have a "describe" block but no "it" blocks inside
+1 to this. Error message:
Versions Jest Config
I am ignoring a couple of files that I am using for set up, they just contain generic beforeAll and afterAll functions that I need in every test file. I am a bit frustrated, I have tried to set up a testing framework for a server and I have now spent more than a day doing it... |
because we can have a "describe" block but no "it" blocks inside
Hmm, should have been fixed. Mind providing a reproduction? |
Im just having this problem and I would like some help:
console.error node_modules/jest-jasmine2/build/jasmine/Env.js:160
Unhandled error
console.error node_modules/jest-jasmine2/build/jasmine/Env.js:161
undefined
Every time I try to run some tests I have it show me that just in macOS and I don’t know how to fix them.
When I try running them on windows theres no errors
… On Apr 13, 2018, at 10:08 AM, Simen Bekkhus ***@***.***> wrote:
Hmm, should have been fixed. Mind providing a reproduction?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#5531 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AiTCqyWdAqcCr0N5yDF0E0v4D5160YVwks5toLFrgaJpZM4SCKO8>.
|
I've never seen that error, unfortunately |
Can you test with |
|
Awesome |
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. |
What is the current behavior?
Jest in watch mode tries to parse results and fails with:
What is the expected behavior?
Jest just logs something like:
without breaking the watch mode and without throwing any errors.
Please provide your exact Jest configuration and mention your Jest, node,
yarn/npm version and operating system.
I don't think this depends on a version of any of those. I will be happy to post them if anyone requests.
The text was updated successfully, but these errors were encountered: