Short Screencasts of Gourmet Ruby, by Avdi Grimm
This code smell, or rather test smell, runs opposite to the fundamental law of mocking, only mock what you own.
In Growing Object-Oriented Software Guided by Tests, Freeman and Pryce go on to say –
Today we learn about how the StringIO class can help us test methods that work with files.
As we continue examining code smells in mockist tests, today we turn our attention to code that mocks out core I/O calls.
Test doubles are a powerful but easy-to-misuse tool for design. In this episode, we look at some tell-tale signes that mocks aren't being used effectively.
At the borders of our systems, mockist testing hits a point of diminishing returns. In this episode we take a look at when to stop mocking and start integration testing.
