Closed
Description
openedon Sep 2, 2022
Version
27.5.1
Steps to reproduce
Repro:
const testMock = {
works: jest.fn().mockImplementation(() => Promise.resolve(undefined)),
fails: jest.fn().mockResolvedValue(undefined),
};
it('test-mockResolvedValue', fakeAsync(async() => {
await testMock.fails();
flush();
expect(true).toBeTrue();
}));
it('test-mockImplementation', fakeAsync(async() => {
await testMock.works();
flush();
expect(true).toBeTrue();
}));
Expected behavior
Both tests are passing without any error, since both should be exactly the same as the Jest-docs are stating that mockFn.mockResolvedValue(value)
is "Syntactic sugar function for" jest.fn().mockImplementation(() => Promise.resolve(value))
.
Actual behavior
Test test-mockResolvedValue
fails on the flush()
due to The code should be running in the fakeAsync zone to call this function
:
Additional context
I feel this problem is linked to #6645 and #11146 .
Environment
System:
OS: Windows 10 10.0.19043
CPU: (12) x64 Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz
Binaries:
Node: 16.16.0 - C:\Program Files\nodejs\node.EXE
npm: 8.11.0 - C:\Program Files\nodejs\npm.CMD
npmPackages:
jest: ^27.2.3 => 27.5.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment