Recordsnpmjest30.4.2
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| alpine musl | 11 | |
|---|---|---|
| expect.arrayContaining | ||
| expect.toEqual | ||
| expect.toStrictEqual | ||
| jest-runtime | ||
| jest.clearAllMocks | ||
| jest.doMock |
Showing the environments with the most evidence.
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Environment detail
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 3✓ · PROJECT_TEST 3✓ — Usage: USED 3✓ — Verified: CONTRACT 15✓
|
HIGH | 6 +3 | 15 | 100% | 1 · 3✓ | 2026-08-30 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-08-16 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 3✓
|
LOW | 3 | 0 | 100% | 1 | 2026-08-16 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-08-16 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 3✓ · PROJECT_TEST 1✓ 3✕
|
ELEVATED FAILURE | 7 | 0 | 57% | 1 | 2026-08-17 |
Recent failure clusters
-
observed PROJECT_TEST Evidence gap ×3 30.4.2 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-17 · Last seen: 2026-08-17Diagnostic re-verification candidate
Symbols
- expect.arrayContaining 1 1 of 1 runs passed
- jest.clearAllMocks 1 2 of 2 runs passed
- jest.doMock 2 4 of 4 runs passed
- jest.dontMock 1 2 of 2 runs passed
- test.each 1
- module.exports 1
- jest.isolateModules 1 2 of 2 runs passed
- jest-runtime 1 2 of 2 runs passed
- jest.resetAllMocks 1 2 of 2 runs passed
- jest.resetModules 1 2 of 2 runs passed
- jest.restoreAllMocks 1
- jest.runCLI
- jest.setSystemTime 1
- jest.spyOn 1
- expect.toEqual 1 2 of 2 runs passed
- expect.toStrictEqual 1 2 of 2 runs passed
- jest.useFakeTimers 1