I personally think that hiding the decision to use a stub vs a mock is a very dangerous idea.
Testing is something that we should be helping others understand. Not trying to down down. A stub vs a mock is a very important decision. In fact I would suggest that it's one of the best ways for a developer to provide information on their intent. If I see a stub I know they were just trying to fulfill some requirement. If I see a mock I know that they considered that call important enough that it needed to be verified. On Fri, Nov 7, 2008 at 7:34 AM, mike <[EMAIL PROTECTED]> wrote: > I think they are redundant and that is what causes confusion. I've been > working on a framework that hides the decisions of to Stub or to Mock behind > the BDD intentions of Given and Should. It might be interesting to look at. > There are a lot of examples @ http://fluentspec.com. > Oren, the implementation also uses Castle's dynamic proxy, therefore it > could be easy to have that kind of syntax in RhinoMocks. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
