A Mock Without an Owner Is a Liability Waiting to Happen
Teams talk a lot about writing mocks and almost never about who owns them afterward. That gap is where a surprising amount of trouble comes from. A mock is a copy of some real dependency, and like any copy it goes stale unless someone is responsible for keeping it true. Most mocks have no such someone. They get written once, in the heat of building a feature, and then quietly orphaned, and an...