Sample
Measure the one-based mock.invocationCallOrder values produced by vi.fn in Vitest 4.0.0
sha256:08ce35c85a89fdd63e12e8a02a77e7a05658eeac84405e357d1360989ffceae3
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Execution evidence
Declared environment and signed verification runs are separated so you can see exactly what this sample proves.
Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS
Declared environment
- Execution context
- node
- Operating system
- linux
- Architecture
- x64
- Runtime
- node
- Language
- node
- Package manager
- npm
Verification-run environments
- Execution context
- node 22
- Operating system
- linux alpine · musl
- Architecture
- x64
- Runtime
- node 22
- Language
- javascript
- Package manager
- npm
- Execution
- container · docker
CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17
Case
- Goal
- Measure the one-based mock.invocationCallOrder values produced by vi.fn in Vitest 4.0.0 HOW
- Packages
-
vitest 4.0.0
- Environment
- node
- Created
- 2026-08-17T03:53:24Z
Commonly assumed
A mock created with vi.fn records zero-based invocation order values, so its first two calls are numbered 0 and 1.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert two calls to one vi.fn mock produce mock.invocationCallOrder equal to [1, 2]
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the source artifact (tar.gz)
Origin Seeder
csx-seed
Verification receipts
- node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9