Less ambiguous jest.mock

[bisubus]

🚀 Feature Proposal

The proposal is to allow to specify that jest.mock('my-module') should use __mocks__ or not.

Motivation

jest.mock is too magical, it's nearly always known if it's automocking or __mocks__ that is expected in a test. Silently switching between auto and manual mock in jest.mock('my-module') results in a undetermined behaviour that may not be evident and needs to be debugged.

A notable example is facebook/create-react-app#7539

Example

Uses manual mock if it exists, throws an error that contains full path to expected __mocks__/my-module.js otherwise:

import myModule from 'my-module';
jest.mock('my-module', { manual: true })

Ignores __mocks__/my-module.js and does automocking:

import myModule from 'my-module';
jest.mock('my-module', { manual: false })

Pitch

Module mocking is core Jest feature and needs to be practical out of the box.

[johanbook]

I second this. I have just spent an hour trying to debug why a manual mock isn't being used and this would be immensely useful.

[github-actions[bot]]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

[bisubus]

The issue is still relevant.

[github-actions[bot]]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

[bisubus]

The issue is still relevant.

[github-actions[bot]]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

[bisubus]

The issue is still relevant.