If there is one testing technique more misunderstood and mis-used than any other, it is stub and mock objects. Sometimes (to, say, an aging and slightly cynical Ruby consultant) it can seem like Ruby codebases break down into one of two camps:
Those that lavishly overuse mocks, mostly against their intended purpose, and
Those written by programmers who have been so burned by the downfalls of unskillful mock object use that they refuse to employ them at all.
The topics that follow will (hopefully) help you to find a middle path between these two extremes, guided by the experience of some of the inventors of mock- and stub-object techniques.
Report
There was a problem reporting this post.
Block Member?
Please confirm you want to block this member.
You will no longer be able to:
See blocked member's posts
Mention this member in posts
Please allow a few minutes for this process to complete.
Responses