Sample
jest.doMock registered inside jest.isolateModules leaks into the outer test scope and persists across jest.resetModules.
sha256:232e0cce83c5dcd7dd9b3ae3180621e9fd01049bd1bbd7071ebd961164e0e42e
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- jest.doMock registered inside jest.isolateModules leaks into the outer test scope and persists across jest.resetModules. HOW
- Packages
- jest 30.4.2
- Environment
- node
- Created
- 2026-08-17T01:55:00Z
Commonly assumed
jest.isolateModules isolates module mocking performed with jest.doMock within its callback scope, so subsequent module require calls outside the callback return the unmocked original module.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Calling jest.doMock inside a jest.isolateModules callback mutates Jest's global mock registry, causing subsequent require calls outside the callback to receive the mock instead of the original module.
- Calling jest.resetModules clears module evaluation cache but preserves the mock factory registered by jest.doMock inside jest.isolateModules.
Files
- NOTES.md
- csx.json
- dependency.cjs
- package-lock.json
- package.json
- subject.cjs
- test/contract.mjs
- test/leak.test.js
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9