My team has been using a mocking framework for a year, but we started with NMock v1 and switched to Rhino Mocks. The switch was a great decision, we all love Rhino, but some of the syntax can be confusing after switching.
We've been having trouble remembering how to set expectation for Write-only Properties and Sub routines so I put together a one page quick reference sheet (.pdf).
Download
Is there a feature of Rhino Mocks that should be included? Keep in mind that it needs to be one page. I don't want to plaster the developers walls with an eight page "quick" reference.
If you don't know the difference between fakes, stubs, mocks, and dummy objects, this post by Jeff Atwood will answer the question and stick in your memory.
posted @ Saturday, February 17, 2007 10:31 PM