Cheap integration tests is usually an oxymoron (when cheap refers to the tightness of the developer feedback loop). Gary was coming from the land of Ruby-on-ra

Cheap integration tests is usually an oxymoron (when cheap refers to the tightness of the developer feedback loop). Gary was coming from the land of Ruby-on-rails where a full set of integration tests could take hours. In that environment, structuring your code to enable easy testing of complex logic makes a lot of sense. Likewise in a large enterprise environment, where integration testing across a (usually messy) set of interconnected dependencies is a pipe dream. It's true that over-architecting is something to be wary of, but as usual, there's no one-size-fits-all answer.