Sometimes you have a method on your mocked object for which you don't care how or if it was called, but you may want to set a return value (or an exception to be thrown) in case it is called. For example, you may have some interaction that you've already verified, or you are testing some other class and just need to get the right value from a method any time it is called. To do this in Rhino Mocks, use SetupResult.For(). Here is the code:
public void SetupResultUsingOrdered()
for (int i = 0; i < 30; i++)
When we use SetupResult.For() we tell Rhino Mocks: "I don't care about this method, it needs to do X, so just do it, but otherwise ignore it." Using SetupResult.For() completely bypasses the expectations model in Rhino Mocks. In the above example, we define demo.Prop to return "Ayende", and we can call it no matter what the currently expected method is.
What about methods returning void?
You would use LastCall.Repeat.Any(), which has identical semantics (ignore ordering, etc).
The opposite of SetupResult.For() is to specify that this method should never be called (useful if you're using dynamic mocks), which is done like this:
This has the same semantics as ExpectNoCall() in NMock and this tells the framework that any call to this method is an error. Notice that I still call IgnoreArguments(), since otherwise the expectation would be specifically that this method never called with null as both parameters. Like SetupResult.For() and Repeat.Any(), using Repeat.Never() transcends ordering.
Note: If you want to have a method that can repeat any number of time, but still obeys ordering, you can use: LastCall.On().Repeat.Times(0,int.MaxValue). This does obey all of the normal rules.
Up: Rhino Mocks Documentation
Next: Rhino Mocks Mocking classes