Hacker News Reader

I have tried using fakes over mocks, but it becomes cumbersome if it is a large-ish code base with handful of developers contributing to it. Keeping expectations on what a particular Fake does gets contentious. Mocks however usually allow a developer to encapsulate entire mock behavior within the boundaries of a unit test.

I am curious to know if you ran into similar problem, if you did how you managed to overcome it?

This seems like an odd assertion to make, since fakes and mocks have largely non-overlapping purposes. Fakes provide some simulacrum of real behavior, while mocks just verify that appropriate messages were sent to the thing they're standing in for.

I do see fakes as having overlapping purpose with stubs, though. But, like the title of the article says, mocks aren't stubs.

Flushing it out or fleshing it out?