Expand Jest setup instructions. #33
Conversation
| ### Jest | ||
| If you are using [jest](https://facebook.github.io/jest/), the simplest setup | ||
| is to use jest's `setupTestFrameworkScriptFile` config. You'll also need to | ||
| tell jest to unmock `react`, `enzyme`, and `enzyme-jest`. |
There was a problem hiding this comment.
enzyme-jest ? do you mean jasmine-enzyme ?
Also. I've never experienced needing jasmine-enzyme in the unmocked module paths. From having a slight understanding of jest's internals, I don't think it would ever be necassary. Could you try removing jasmine-enzyme from your unmockedModulePathPatterns and see if it fails?
There was a problem hiding this comment.
Oops sorry, that should indeed be jasmine-enzyme.
I get the following error when removing jasmine-enzyme from unmockedModulePathPatterns
TypeError: expect(...).toHaveText is not a function
This is of course when using the .toHaveText() assertion. I get the same kind of error message with any of the jasmine-enzyme assertions.
There was a problem hiding this comment.
Ah. I bet it's working for me because I put just "enzyme" in my unmocked path. Which regex matches "jasmine-enzyme". But it's probably better for the docs to be explicit.
* `enzyme` and `jasmine-enzyme` must be unmocked.
|
@blainekasten Makes sense, I rebased the commit to incorporate the changes and fix the typo mentioned earlier. |
|
Thanks so much! |
#32
I ran into some cryptic error messages when I didn't add
enzymeandjasmine-enzymeto jest's unmocked module list.This PR adds an explicit mention in the jest setup docs that you need to unmock these modules.
@blainekasten