Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(@jest/mock): Add withImplementation #13281

Merged
merged 16 commits into from Sep 23, 2022
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
Expand Up @@ -2,6 +2,7 @@

### Features

- `[@jest/mock]` Add `withImplementation` method for temporarily overriding a mock.
jeppester marked this conversation as resolved.
Show resolved Hide resolved
- `[@jest/environment, jest-runtime]` Allow `jest.requireActual` and `jest.requireMock` to take a type argument ([#13253](https://github.com/facebook/jest/pull/13253))
- `[@jest/environment]` Allow `jest.mock` and `jest.doMock` to take a type argument ([#13254](https://github.com/facebook/jest/pull/13254))
- `[@jest/fake-timers]` Add `jest.now()` to return the current fake clock time ([#13244](https://github.com/facebook/jest/pull/13244), [13246](https://github.com/facebook/jest/pull/13246))
Expand Down
6 changes: 6 additions & 0 deletions packages/jest-mock/README.md
Expand Up @@ -98,3 +98,9 @@ In case both `.mockImplementationOnce()` / `.mockImplementation()` and `.mockRet

- if the last call is `.mockReturnValueOnce()` or `.mockReturnValue()`, use the specific return value or default return value. If specific return values are used up or no default return value is set, fall back to try `.mockImplementation()`;
- if the last call is `.mockImplementationOnce()` or `.mockImplementation()`, run the specific implementation and return the result or run default implementation and return the result.

##### `.withImplementation(function, callback)`
jeppester marked this conversation as resolved.
Show resolved Hide resolved

Temporarily overrides the default mock implementation within the callback, then restores it's previous implementation.

If the callback is async or returns a promise like object, `withImplementation` will return a promise. Awaiting the promise will await the callback and reset the implementation.
jeppester marked this conversation as resolved.
Show resolved Hide resolved
53 changes: 53 additions & 0 deletions packages/jest-mock/src/__tests__/index.test.ts
Expand Up @@ -1073,6 +1073,59 @@ describe('moduleMocker', () => {
});
});

describe('withImplementation', () => {
it('sets an implementation which is available within the callback', async () => {
jeppester marked this conversation as resolved.
Show resolved Hide resolved
jeppester marked this conversation as resolved.
Show resolved Hide resolved
const mock1 = jest.fn();
const mock2 = jest.fn();

const Module = jest.fn(() => ({someFn: mock1}));
const testFn = function () {
const m = new Module();
m.someFn();
};

Module.withImplementation(
() => ({someFn: mock2}),
() => {
testFn();
expect(mock2).toHaveBeenCalled();
expect(mock1).not.toHaveBeenCalled();
},
);

testFn();
expect(mock1).toHaveBeenCalled();
});

it('returns a promise if the provided callback is asynchronous', async () => {
jeppester marked this conversation as resolved.
Show resolved Hide resolved
const mock1 = jest.fn();
const mock2 = jest.fn();

const Module = jest.fn(() => ({someFn: mock1}));
const testFn = function () {
const m = new Module();
m.someFn();
};

const promise = Module.withImplementation(
() => ({someFn: mock2}),
async () => {
testFn();
expect(mock2).toHaveBeenCalled();
expect(mock1).not.toHaveBeenCalled();
},
);

// Is there a better way to detect a promise?
jeppester marked this conversation as resolved.
Show resolved Hide resolved
expect(typeof promise.then).toBe('function');

await promise;

testFn();
expect(mock1).toHaveBeenCalled();
});
});

test('mockReturnValue does not override mockImplementationOnce', () => {
const mockFn = jest
.fn()
Expand Down
40 changes: 40 additions & 0 deletions packages/jest-mock/src/index.ts
Expand Up @@ -124,6 +124,12 @@ type RejectType<T extends FunctionLike> = ReturnType<T> extends PromiseLike<any>
? unknown
: never;

type WithImplementationSyncCallbackReturn = void | undefined;
type WithImplementationAsyncCallbackReturn = Promise<unknown>;
type WithImplementationCallbackReturn =
| WithImplementationSyncCallbackReturn
| WithImplementationAsyncCallbackReturn;
jeppester marked this conversation as resolved.
Show resolved Hide resolved

export interface MockInstance<T extends FunctionLike = UnknownFunction> {
_isMockFunction: true;
_protoImpl: Function;
Expand All @@ -135,6 +141,12 @@ export interface MockInstance<T extends FunctionLike = UnknownFunction> {
mockRestore(): void;
mockImplementation(fn: T): this;
mockImplementationOnce(fn: T): this;
withImplementation<R extends WithImplementationCallbackReturn>(
fn: T,
callback: () => R,
): R extends WithImplementationAsyncCallbackReturn
? Promise<void>
: undefined;
jeppester marked this conversation as resolved.
Show resolved Hide resolved
mockName(name: string): this;
mockReturnThis(): this;
mockReturnValue(value: ReturnType<T>): this;
Expand Down Expand Up @@ -768,6 +780,34 @@ export class ModuleMocker {
return f;
};

f.withImplementation = <R extends WithImplementationCallbackReturn>(
fn: UnknownFunction,
callback: () => R,
// @ts-expect-error: Type guards are not advanced enough for this use case
): R extends WithImplementationAsyncCallbackReturn
? Promise<void>
: undefined => {
jeppester marked this conversation as resolved.
Show resolved Hide resolved
// Remember previous mock implementation, then set new one
const mockConfig = this._ensureMockConfig(f);
const previousImplementation = mockConfig.mockImpl;
mockConfig.mockImpl = fn;

const returnedValue = callback();

if (
typeof returnedValue === 'object' &&
returnedValue !== null &&
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
typeof returnedValue === 'object' &&
returnedValue !== null &&
returnedValue != null &&
typeof returnedValue === 'object' &&

probably doesn't matter, but easier to bail out early

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. Like I mentioned in one of my previous comments I copied this verbatim from jest circus.

So there's probably a nice tiny performance enhancement waiting to be made there as well:
https://github.com/facebook/jest/blob/a20fd859673800c50f8f089cfb4a87faec119525/packages/jest-circus/src/utils.ts#L271-L275

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

haha, the linked SO answer says not to use it 🙈

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opened #13314

typeof returnedValue.then === 'function'
) {
jeppester marked this conversation as resolved.
Show resolved Hide resolved
// @ts-expect-error: Type guards are not advanced enough for this use case
return returnedValue.then(() => {
mockConfig.mockImpl = previousImplementation;
});
} else {
mockConfig.mockImpl = previousImplementation;
}
};

f.mockImplementation = (fn: UnknownFunction) => {
// next function call will use mock implementation return value
const mockConfig = this._ensureMockConfig(f);
Expand Down