示例
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
案例
- 目标
- jest.doMock registered inside jest.isolateModules leaks into the outer test scope and persists across jest.resetModules. HOW
- 包
- jest 30.4.2
- 环境
- node
- 创建时间
- 2026-08-17T01:55:00Z
常见的想当然
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.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- 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.
文件
- NOTES.md
- csx.json
- dependency.cjs
- package-lock.json
- package.json
- subject.cjs
- test/contract.mjs
- test/leak.test.js
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9