debug-failing-test

Add targeted console.log statements with a [DEBUG] label around the suspicious code, run the test, and compare logged values against expectations. Repeat with narrower logging until the divergence point reveals the root cause, then fix and remove all debug statements.

Start at the failing assertion and work backwards through the values it compares. Log inputs, intermediate states, and return values before and after key operations to locate where actual behavior diverges from expected behavior.

Tests often fail because mocks return unexpected values or are not reset between cases. Log the mock return values during the test run and verify the setup and teardown code configures them as the source code expects.

Yes, add timestamps to debug logs when timing might be relevant and log before and after awaited operations. Comparing the order and timing of logged events exposes race conditions and unhandled promises.

Remove every debug log and temporary variable added during diagnosis, then re-run the test and related tests to confirm no regressions. Finally, summarize the bug and fix, and record the learning in the relevant instruction file.