http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Hand coded mocks or stubs are also the way to go if you find yourself re-using that particular fake object in multiple tests and/or fixtures. You could use RhinoMocks in a common setup method, but I often find in these cases there are just too many methods or interactions to warrant mocking in a meaningful manner, especially when Re# will quite quickly produce an implementation of an interface. Perhaps this is just a code smell? I generally find that hand coded fake objects are easier to deal with and understand when you have more than just a few lines of code to setup a mock, like in your example. After all, not everything is a nail. http://ayende.com/3399/where-mocking-fails#comment1http://ayende.com/3399/where-mocking-fails#comment1Wed, 02 Jul 2008 23:11:55 GMT