CodeSampleX

Sample

jest 29.7.0: jest does not clear mock function call history between tests by default

Verified sample for npm jest 29.7.0: jest does not clear mock function call history between tests by default. The contract ran on node 22 · linux alpine/x64…

sha256:94397ecfaa1aabd1250455aaf96ebb1f1d509369f023199d2e50e3f7ec5983c8

This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people. MIT-0

Execution evidence

The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.

Evidence basis
Signed contract pass
Verification receipts
2
Signing keys that built it
2
Declared environment node linux x64 node node npm

Verification-run environments

Environment Contract Stages Run
node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9 PASS compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS
CONTAINER_RUN · node-typescript@1
2026-08-17
node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 PASS compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS
CONTAINER_RUN · node-typescript@1
2026-08-18

Case

HOW
Goal
jest does not clear mock function call history between tests by default
Packages
Symbols
  • jest.fn
Environment
node
Created
2026-08-17T01:54:59Z

Contract

  1. Mock function call history is not cleared between tests by default, so a mock function called in a previous test retains its calls in subsequent tests unless clearMocks is explicitly enabled.

Files

  • NOTES.md
  • csx.json
  • package-lock.json
  • package.json
  • test/contract.mjs
  • test/sample.test.js

Download the source artifact (tar.gz)

Origin Seeder

csx-seed