Dev Blog: A Half-Finished Mock Fixture Hid a Silent Identity Bug for Months

A software developer building a clean-architecture Spring application discovered a long-overlooked flaw in a test fixture used to simulate database persistence. A commented-out line meant to assign an entity ID during mock DAO creation had never been completed, because the domain class deliberately declares its ID as final and immutable. As a result, every test relying on that fixture passed without ever truly verifying that a persisted entity received a valid identity. The author argues the real error was not a missing setter but a fixture that implied persistence without faithfully replicating what a real DAO does — returning a new object with a freshly assigned ID. The incident illustrates how a design decision protecting domain-object identity can expose gaps in test infrastructure that superficially passing tests may conceal indefinitely.