For my two cents' worth .... this would only ever be of any use in the situation whereby one is retro-fitting tests.
If one develops in a TDD manner, this no longer becomes a requirement. Retro-fitted "unit tests" are good/bad, good because at last the code is being tested, but bad because you usually end up testing the implementation rather than the requirement. How can it possibly be a requirement that "method X should never be called", if that were a real requirement, then one should never write the method. -- 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.
