Функції-імітації
Функції-імітації ще називають "шпигунами", ос кільки вони дозволяють слідкувати за поведінкою функції, непрямо викликаною іншим кодом, а не лише перевіряти результат. Ви можете створити функцію-імітацію за допомогою jest.fn()
. Якщо не задано реалізацію, вона повертатиме undefined
після виконання.
Приклади TypeScript з цієї сторінки будуть працювати, як задокументовано, тільки якщо ви явно імпортуєте Jest API:
import {expect, jest, test} from '@jest/globals';
Інструкцію щодо налаштування Jest за допомогою TypeScript можна знайти на сторінці Початок роботи.
Методи
- Довідка
mockFn.getMockName()
mockFn.mock.calls
mockFn.mock.results
mockFn.mock.instances
mockFn.mock.contexts
mockFn.mock.lastCall
mockFn.mockClear()
mockFn.mockReset()
mockFn.mockRestore()
mockFn.mockImplementation(fn)
mockFn.mockImplementationOnce(fn)
mockFn.mockName(name)
mockFn.mockReturnThis()
mockFn.mockReturnValue(value)
mockFn.mockReturnValueOnce(value)
mockFn.mockResolvedValue(value)
mockFn.mockResolvedValueOnce(value)
mockFn.mockRejectedValue(value)
mockFn.mockRejectedValueOnce(value)
mockFn.withImplementation(fn, callback)
- Замінені властивості
- Використання TypeScript
Довідка
mockFn.getMockName()
Повертає рядок з іменем імітації, встановленим за допомогою .mockName()
.
mockFn.mock.calls
An array containing the call arguments of all calls that have been made to this mock function. Each item in the array is an array of arguments that were passed during the call.
For 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:
[
['arg1', 'arg2'],
['arg3', 'arg4'],
];
mockFn.mock.results
An array containing the results of all calls that have been made to this mock function. Each entry in this array is an object containing a type
property, and a value
property. type
will be one of the following:
'return'
- вказує на виклик, що завершився звичайним поверненням.'throw'
- вказує на виклик, по завершенню якого кидається значення.'incomplete'
- вказує на поки що незавершений виклик. Це відбувається, якщо ви перевіряєте результат зсередини самої функції-імітації або функції, що була нею викликана.
The value
property contains the value that was thrown or returned. value
is undefined when type === 'incomplete'
.
For example: A mock function f
that has been called three times, returning 'result1'
, throwing an error, and then returning 'result2'
, would have a mock.results
array that looks like this:
[
{
type: 'return',
value: 'result1',
},
{
type: 'throw',
value: {
/* Error instance */
},
},
{
type: 'return',
value: 'result2',
},
];
mockFn.mock.instances
An array that contains all the object instances that have been instantiated from this mock function using new
.
For example: A mock function that has been instantiated twice would have the following mock.instances
array:
const mockFn = jest.fn();
const a = new mockFn();
const b = new mockFn();
mockFn.mock.instances[0] === a; // true
mockFn.mock.instances[1] === b; // true
mockFn.mock.contexts
An array that contains the contexts for all calls of the mock function.
A context is the this
value that a function receives when called. The context can be set using Function.prototype.bind
, Function.prototype.call
or Function.prototype.apply
.
Наприклад:
const mockFn = jest.fn();
const boundMockFn = mockFn.bind(thisContext0);
boundMockFn('a', 'b');
mockFn.call(thisContext1, 'a', 'b');
mockFn.apply(thisContext2, ['a', 'b']);
mockFn.mock.contexts[0] === thisContext0; // true
mockFn.mock.contexts[1] === thisContext1; // true
mockFn.mock.contexts[2] === thisContext2; // true
mockFn.mock.lastCall
An array containing the call arguments of the last call that was made to this mock function. If the function was not called, it will return undefined
.
For 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.lastCall
array that looks like this:
['arg3', 'arg4'];
mockFn.mockClear()
Clears all information stored in the mockFn.mock.calls
, mockFn.mock.instances
, mockFn.mock.contexts
and mockFn.mock.results
arrays. Often this is useful when you want to clean up a mocks usage data between two assertions.
The clearMocks
configuration option is available to clear mocks automatically before each tests.
Beware 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.
mockFn.mockReset()
Does everything that mockFn.mockClear()
does, and also replaces the mock implementation with an empty function, returning undefined
.
The resetMocks
configuration option is available to reset mocks automatically before each test.
mockFn.mockRestore()
Does everything that mockFn.mockReset()
does, and also restores the original (non-mocked) implementation.
This is useful when you want to mock functions in certain test cases and restore the original implementation in others.
The restoreMocks
configuration option is available to restore mocks automatically before each test.
mockFn.mockRestore()
only works when the mock was created with jest.spyOn()
. Thus you have to take care of restoration yourself when manually assigning jest.fn()
.
mockFn.mockImplementation(fn)
Accepts a function that should be used as the implementation of the mock. The mock itself will still record all calls that go into and instances that come from itself – the only difference is that the implementation will also be executed when the mock is called.
jest.fn(implementation)
is a shorthand for jest.fn().mockImplementation(implementation)
.
- JavaScript
- TypeScript
const mockFn = jest.fn(scalar => 42 + scalar);
mockFn(0); // 42
mockFn(1); // 43
mockFn.mockImplementation(scalar => 36 + scalar);
mockFn(2); // 38
mockFn(3); // 39