Count the Clocks Before Characterization Tests: A Nondeterminism Census for Messy Repos
This story is from 2026-10-27. It is preserved in the archive; the latest stories are on the live feed.
Characterization tests fail for a boring reason: the code reads the wall clock. You cannot pin behavior you cannot reproduce twice. So count the clocks first, then move code. There is a second trap. unittest.mock.patch targets a dotted path, not an object. A refactor that moves a module silently br…
Read the full story at DEV Community — AI ↗
Timeline · 1 report
- 2026-10-27 09:37 · DEV Community — AI
Count the Clocks Before Characterization Tests: A Nondeterminism Census for Messy Repos