示例
Differentiate jest.resetAllMocks, jest.restoreAllMocks, and jest.clearAllMocks behavior on spied methods
sha256:5873cc2e5b1f64ed7fe5e2abab9bb1bfcf695edf94fcc807dd4099b64e4b49a3
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Differentiate jest.resetAllMocks, jest.restoreAllMocks, and jest.clearAllMocks behavior on spied methods HOW
- 包
- jest 30.4.2
- 环境
- node
- 创建时间
- 2026-08-17T01:53:39Z
常见的想当然
Calling jest.resetAllMocks() restores functions spied on with jest.spyOn() back to their original unmocked implementation.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- jest.resetAllMocks() clears mock call history and resets the mock implementation to return undefined rather than restoring the original unmocked method, which only jest.restoreAllMocks() or spy.mockRestore() performs.
- jest.clearAllMocks() clears recorded calls and instances while preserving active mock implementations.
- jest.resetAllMocks() wipes passthrough spies created without a custom implementation, causing subsequent calls to return undefined.
- Jest runner executes test suites verifying that jest.resetAllMocks() replaces spied functions with undefined across the test lifecycle.
文件
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
- test/fixture.test.js
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9