vitest-mock-extended

> Type safe mocking extensions for Vitest ✅


THIS IS A FORK OF jest-mock-extended ALL CREDITS GO TO THE ORIGINAL AUTHOR

Features

- Provides complete Typescript type safety for interfaces, argument types and return types
- Ability to mock any interface or object
- calledWith() extension to provide argument specific expectations, which works for objects and functions.
- Extensive Matcher API compatible with Jasmine matchers
- Supports mocking deep objects / class instances.
- Familiar Jest like API

Installation

``bash
npm install vitest-mock-extended --save-dev
`

or

`bash
yarn add vitest-mock-extended --dev
`

If ReferenceError: vi is not defined related error occurs, please set globals: true.

Example

`ts
import { mock } from 'vitest-mock-extended';

interface PartyProvider {
getPartyType: () => string;
getSongs: (type: string) => string[];
start: (type: string) => void;
}

describe('Party Tests', () => {
test('Mock out an interface', () => {
const mock = mock();
mock.start('disco party');

expect(mock.start).toHaveBeenCalledWith('disco party');
});

test('mock out a return type', () => {
const mock = mock();
mock.getPartyType.mockReturnValue('west coast party');

expect(mock.getPartyType()).toBe('west coast party');
});

test('Can specify fallbackMockImplementation', () => {
const mockObj = mock(
{},
{
fallbackMockImplementation: () => {
throw new Error('not mocked');
},
}
);

expect(() => mockObj.getSomethingWithArgs(1, 2)).toThrowError('not mocked');
});
});
`

Assigning Mocks with a Type

If you wish to assign a mock to a variable that requires a type in your test, then you should use the MockProxy<> type
given that this will provide the apis for calledWith() and other built-in vitest types for providing test functionality.

`ts
import { MockProxy, mock } from 'vitest-mock-extended';

describe('test', () => {
let myMock: MockProxy;

beforeEach(() => {
myMock = mock();
})

test(() => {
myMock.calledWith(1).mockReturnValue(2);
...
})
});

`

calledWith() Extension

vitest-mock-extended allows for invocation matching expectations. Types of arguments, even when using matchers are type checked.

`ts
const provider = mock();
provider.getSongs.calledWith('disco party').mockReturnValue(['Dance the night away', 'Stayin Alive']);
expect(provider.getSongs('disco party')).toEqual(['Dance the night away', 'Stayin Alive']);

// Matchers
provider.getSongs.calledWith(any()).mockReturnValue(['Saw her standing there']);
provider.getSongs.calledWith(anyString()).mockReturnValue(['Saw her standing there']);
`

You can also use mockFn() to create a vi.fn() with the calledWith extension:

`ts
type MyFn = (x: number, y: number) => Promise;
const fn = mockFn();
fn.calledWith(1, 2).mockReturnValue('str');
`

Clearing / Resetting Mocks

vitest-mock-extended exposes a mockClear and mockReset for resetting or clearing mocks with the same
functionality as vi.fn().

`ts
import { mock, mockClear, mockReset } from 'vitest-mock-extended';

describe('test', () => {
const mock: UserService = mock();

beforeEach(() => {
mockReset(mock); // or mockClear(mock)
});
...
})
`

Deep mocks

If your class has objects returns from methods that you would also like to mock, you can use mockDeep in
replacement for mock.

`ts
import { mockDeep } from 'vitest-mock-extended';

const mockObj: DeepMockProxy = mockDeep();
mockObj.deepProp.getNumber.calledWith(1).mockReturnValue(4);
expect(mockObj.deepProp.getNumber(1)).toBe(4);
`

if you also need support for properties on functions, you can pass in an option to enable this

`ts
import { mockDeep } from 'vitest-mock-extended';
const mockObj: DeepMockProxy = mockDeep({ funcPropSupport: true });
mockObj.deepProp.calledWith(1).mockReturnValue(3);
mockObj.deepProp.getNumber.calledWith(1).mockReturnValue(4);
expect(mockObj.deepProp(1)).toBe(3);
expect(mockObj.deepProp.getNumber(1)).toBe(4);
`

You can also provide a fallback mock implementation to be used if you do not define a return value using calledWith.

`ts
import { mockDeep } from 'jest-mock-extended';
const mockObj = mockDeep({
fallbackMockImplementation: () => {
throw new Error('please add expected return value using calledWith');
},
});
expect(() => mockObj.getNumber()).toThrowError('not mocked');
`

Mocked Type Helpers


If you mock objects/functions of modules and can't refer them directly due to hoist,
mocked type helpers can be used. This is similar to the use case of Vitest's vi.mocked
`ts
// APIs
import { mocked, mockedFn } from "vitest-mock-extended";
import { originalObj, originalFn} from "somewhere";

const mockedObj = mocked(originalObj);
const deepMockedObj = mocked(originalObj, true);
const mockedFunction = mockedFn(originalFn);
`

An example would be
`ts
// Mock a module
// @/libs/example.mock.ts
import { mock } from "vitest-mock-extended";
import { ExampleClient } from "@/libs/example";

vi.mock(import("@/libs/example"), async (importOriginal) => {
const actual = await importOriginal();
return {
...actual,
// Due to vi.mock being hoisted, we have to mock here directly instead of
// defining an exampleMock outside and assign it to example
example: mock(),
};
});

// Use the mocked object
import "@/libs/example.mock"; // Mock out the actual client
import { mocked } from "vitest-mock-extended";
import { example } from "@/libs/example";

const exampleMock = mocked(example);

test("send notification", () => {
example.function.mockResolvedValue(xxx);
...
}
`

Available Matchers

| Matcher | Description |
| ---------------------- | ---------------------------------------------------------- |
| any() | Matches any arg of any type. |
| anyBoolean() | Matches any boolean (true or false) |
| anyString() | Matches any string including empty string |
| anyNumber() | Matches any number that is not NaN |
| anyFunction() | Matches any function |
| anyObject() | Matches any object (typeof m === 'object') and is not null |
| anyArray() | Matches any array |
| anyMap() | Matches any Map |
| anySet() | Matches any Set |
| isA(class) | e.g isA(DiscoPartyProvider) |
| includes('value') | Checks if value is in the argument array |
| containsKey('key') | Checks if the key exists in the object |
| containsValue('value') | Checks if the value exists in an object |
| has('value') | checks if the value exists in a Set |
| notNull() | value !== null |
| notUndefined() | value !== undefined |
| notEmpty() | value !== undefined && value !== null && value !== '' |
| captor() | Used to capture an arg - alternative to mock.calls[0][0] |

Writing a Custom Matcher

Custom matchers can be written using a MatcherCreator

`ts
import { MatcherCreator, Matcher } from 'vitest-mock-extended';

// expectedValue is optional
export const myMatcher: MatcherCreator = (expectedValue) =>
new Matcher((actualValue) => {
return expectedValue === actualValue && actualValue.isSpecial;
});
`

By default, the expected value and actual value are the same type. In the case where you need to type the expected value
differently than the actual value, you can use the optional 2 generic parameter:

`ts
import { MatcherCreator, Matcher } from 'vitest-mock-extended';

// expectedValue is optional
export const myMatcher: MatcherCreator = (expectedValue) =>
new Matcher((actualValue) => {
return actualValue.includes(expectedValue);
});
``