Mocking with rhino mocks follow up
This is just a quick follow up to my Mocking with Rhino Mocks post.
You can see the entire thread here, but the essence of it is this.
DynamicMock creates a mock where all unexpected calls are ignored with no error. So, if we were to create a dynamic mock and then set an expectation that a method on it is called twice, there would be a requirement for two calls, but a third cal would just be ignored rather than cause an error.
If we absolutely want the behavior of an exact number of calls, then use CreateMock instead of DynamicMock. Nice and simple solution :)