Tests crash when requiring React Addons about jest

[vjeux]

I got the same issue and fixed it by unmocking React. See http://facebook.github.io/jest/docs/tutorial-react.html#setup Can you tell me if it fixes it

[feifanzhou]

Fantastic — that works, thanks! Is it a bug to be fixed, or is it intentional (and should be documented)?

[vjeux]

This is intentional, React is not meant to be mocked when tested against. But we can definitively do a better job at failing when it's not the case. This error is very cryptic

[jeffmo]

Yea, I've been tracking this confusing error message here: #14

This week and last have been super busy for me, so I haven't had a chance to dive in to it just yet, but I'll throw it to the top of the queue since I think it should be a fairly simple fix.

If you have further questions or concerns, lets continue the thread in #14 to keep things centralized.

[feifanzhou]

Sounds good. I'd seen that issue earlier, but the title is misleading (in this case, there's nothing to do with module.exports). Maybe the scope/wording of #14 can be expanded?

[jeffmo]

That's a good point -- I'll update the title

[mindjuice]

I am seeing what appears to be the same issue in Jest V0.4, but I've added the unockedModulePathPatterns entry as @vjeux suggested. Here is the jest section from my package.json file:

"jest": {
  "scriptPreprocessor": "<rootDir>/preprocessor.js",
  "unmockedModulePathPatterns": [
    "<rootDir>/node_modules/react"
  ],
  "testFileExtensions": [
    "js"
  ],
  "moduleFileExtensions": [
    "js",
    "json"
  ]

I'm just using the test files at the moment with the CheckboxWithLabel component, and it is seg faulting. I'm just following this example: https://facebook.github.io/jest/docs/tutorial-react.html#content

node -v
v0.12.0

npm -v
2.5.1

jest -v
v0.4.0

[mindjuice]

Seems I am probably seeing #243 / #266

[github-actions]

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.