Are you able to use the AssertWasNotCalled() extension method? You can use this to check that the method was not called at the end of the test.
Regards, David On Sat, Feb 26, 2011 at 7:49 AM, Mickey <[email protected]> wrote: > One suggestion if I may, when you have a Dynamic Mock, it allows all > methods to be called, however it would be good to be able to set up > the expectation that a particular method will NOT be called. > > Currently the only way of doing that is to have a Strict mock, and > then the need to be explicit about all expected calls. However with > the feature I mentioned one could set up a Dynamic mock, and the > expectation that the method can call whatever it likes, but it must > NOT call this one particular method, and if that excluded method is > called then to be a test fail. > > As I said, the strict mock does this, but then forces a lot of extra > work, having the feature would make it easier to set up the scenario. > As I said its just a suggestion but it would be good to see if anyone > else can see value for this feature / or indeed some other way of > achieving it. > > Thanks. > > -- > 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. > > -- 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.
