Virtual mocks cannot be unmocked

[Blasz]

🐛 Bug Report

After a virtual mock has been created via jest.doMock(..., ..., { virtual: true }) cannot be unmocked via jest.dontMock(...).

The use case for this is when I am testing a module that dynamically requires another module. I have created a virtual mock to test this functionality but want to unmock it in the same test suite so that I can test the error state when the module does not exist.

To Reproduce

Steps to reproduce the behavior:

1. Call jest.doMock('abc', () => ({ foo: jest.fn() }), { virtual: true }); in one test.
2. Call jest.dontMock('abc'); in a subsequent test.
3. Call require('abc') and observe that it returns the virtual mock still

Expected behavior

The virtual mock should not exist anymore and the require call should throw an error.

Link to repl or repo (highly encouraged)

https://repl.it/repls/AjarIdealConfig

Run npx envinfo --preset jest

Paste the results here:

  System:
    OS: macOS Mojave 10.14.4
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
  Binaries:
    Node: 10.9.0 - ~/.nvm/versions/node/v10.9.0/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.2.0 - ~/.nvm/versions/node/v10.9.0/bin/npm
  npmPackages:
    jest: ^24.4.0 => 24.4.0

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.