The restoreMocks configuration option is available to restore mocks automatically before each test. Thus you have to take care of restoration yourself when manually assigning jest.fn(). This is useful when you want to mock functions in certain test cases and restore the original implementation in others.īeware that mockFn.mockRestore() only works when the mock was created with jest.spyOn(). mockFn.mockRestore() ĭoes everything that mockFn.mockReset() does, and also restores the original (non-mocked) implementation. The resetMocks configuration option is available to reset mocks automatically before each test. (Note that resetting a spy will result in a function with no return value).

This is useful when you want to completely reset a mock back to its initial state. mockFn.mockReset() ĭoes everything that mockFn.mockClear() does, and also removes any mocked return values or implementations. The clearMocks configuration option is available to clear mocks automatically before each tests. Often this is useful when you want to clean up a mocks usage data between two assertions.īeware that mockFn.mockClear() will replace mockFn.mock, not just reset the values of its properties! You should, therefore, avoid assigning mockFn.mock to other variables, temporary or not, to make sure you don't access stale data. Each item in the array is an array of arguments that were passed during the call.įor example: A mock function f that has been called twice, with the arguments f('arg1', 'arg2'), and then with the arguments f('arg3', 'arg4'), would have a mock.calls array that looks like this:Ĭlears all information stored in the, , and arrays.

Īn array containing the call arguments of all calls that have been made to this mock function. Returns the mock name string set by calling. mockFn.withImplementation(fn, callback).

Jest clear all mocks