Yes it helps. And you are correct, we are stubbing the IJobQueue and using depency injection so we can test various parts of the main processing class, so the AddNewJobQueueRow method is called from CreateJobQueueForCustomer method.
However, I still have one question, isn't the method AddNewJobQueueRow still getting called whether I stub it or create an expectation for it? To me, whether Rhino Mocks intercepts it and executes my stubbed implementation or the actual original implementation is used, the method is still getting called. So from Rhino Mock's perspective, providing a stub for a method and then executing that stub is not the same as executing the actual method when we're testing for AssertWasCalled? Nate -- You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhinomocks?hl=en.
