Incident Dossier

Spy Counter Survives Reset

A spy helper is used by several tests. After the first test runs, the second test sees an empty call log but the invocation count is non-zero, hinting that the reset is missing one of the two pieces of state.

Initial failing signalinvocation count disagrees with the call log after resetSpyExpected behavior: getInvocationCount() is 0 right after resetSpy · actual behavior: getInvocationCount() is 2, the leftover from the previous test

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Trace what resetSpy touches and what it leaves alone.
Compare the two pieces of state the spy maintains.
Reset both pieces so each test starts from a clean baseline.

Focus Mode

Start

src/spy.js

Likely area

src/spy.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicReliability

DifficultyMedium

Est. time16 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace