Hello, I just spent about 50min working on an elusive problem in which a mocked repository FindAll call was not returning what I expected. I finally figured out that I had set up a Stub in the constructor for my test that returned an empty list, so that my controller didn't throw stack traces during tests that didn't exercise this repository; as such, any subsequent Stub or Expect calls for the same repository were never being called. It would be helpful to receive an exception as soon as the runtime encounters an expectation trying to supersede an earlier Stub/Expect call. Would such functionality conflict with other intentions of the Rhino.Mocks framework?
Thanks. -- "Injustice anywhere is a threat to justice everywhere." Martin Luther King, Jr. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
