We've been using
Rhino Mocks as our mocking framework for the last year and have had some good success with it. Previously, we were writing our mocks by hand, which was a major pain in the ass. While Rhino Mocks offers a lot of great features and has aided our testing efforts in many ways, it has also caused us some pain. I've recently been hearing a lot of "buzz" about
Moq, a new mocking framework developed by
kzu. This morning I read Daniel's "
Why do we need another .NET mocking framework" post and I'm convinced that I need to give Moq a try. A lot of the points in his article ring true to me, and make me wonder if I would prefer Moq over Rhino Mocks. The interesting thing with trying a new mocking framework when you're involved in a large project that has already made a considerable investment in another mocking framework (Rhino Mocks) is how you go about trying it, and what you do if you prefer it to what we're currently using. Ah the joys of software development.
I found the following links on the Moq google code homepage interesting: