Mocking

Mocks Can Leave You Tightly Coupled to the Implementation

We usually say it’s better to test behaviour, not implementation details; test what happens, not how you do it. Mocks often end up erring too much on the side of the "how" rather than the "what". ->

There’s more detailed discussion of the pros and cons of mocks in later chapters. ->