Stefan's point actually supports mine. The idea with mocking
frameworks is to make them as straightforward as possible. The
beginner user shouldn't have to know the difference between a Strict
and Dynamic mock in order to set expectations correctly. If there's
one criticism of Rhino Mocks I have, it's that developers haven't paid
enough attention to making it easy for the beginner to start using.
Everywhere you turn, there seems to be a special exception that
frustratingly causes your mocked objects to fail tests, or multiple
ways of coding the same thing.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
