Bypassing module mocks
Jest allows you to mock out whole modules in your tests, which can be useful for testing if your code is calling functions from that module correctly. However, sometimes you may want to use parts of a mocked module in your test file, in which case you want to access the original implementation, rather than a mocked version.
Consider writing a test case for this createUser
function:
Your test will want to mock the fetch
function so that we can be sure that it gets called without actually making the network request. However, you'll also need to mock the return value of fetch
with a Response
(wrapped in a Promise
), as our function uses it to grab the created user's ID. So you might initially try writing a test like this:
However, if you ran that test you would find that the createUser
function would fail, throwing the error: TypeError: response.text is not a function
. This is because the Response
class you've imported from node-fetch
has been mocked (due to the jest.mock
call at the top of the test file) so it no longer behaves the way it should.
To get around problems like this, Jest provides the jest.requireActual
helper. To make the above test work, make the following change to the imports in the test file:
This allows your test file to import the actual Response
object from node-fetch
, rather than a mocked version. This means the test will now pass correctly.