I am talking about the differences between state and interactions, however for the vast majority of cases I believe that interaction based test are over used.
However I am going to cover it. On Mon, Oct 20, 2008 at 3:06 PM, Shane Courtrille <[EMAIL PROTECTED] > wrote: > The problem I see with that is that you're putting a tool into their hands > without them > really understanding the basic concepts. At the end of the day testing is > not easy. > > There are some concepts that people need to understand. State vs > Interaction testing > is a very big deal and I think that Stub vs Mock is where the two are > separated. If you are > trying to teach people about Rhino Mocks without starting them off with an > explanation > as to the different type of testing (aka State vs Interaction) and where > uses one vs the other > then you are missing a valuable chance to increase their knowledge. > > > On Mon, Oct 20, 2008 at 9:37 AM, Tim Barcz <[EMAIL PROTECTED]> wrote: > >> Good point....forgot about PropertyBehavior (but in this case isn't that >> behavior on a stub an augmentation of a mock's behavior? On the Rhino site >> it says you can do property behavior but that it gets tedious, so instead >> you can just do a stub.) >> >> I was hoping to simplify the concepts for the attendees of my Rhino >> presentation. That's the goal, to get more people testing with Rhino. >> >> >> >> On Mon, Oct 20, 2008 at 10:26 AM, naraga <[EMAIL PROTECTED]> wrote: >> >>> >>> then i think it is too oversimplified. stubs in rhino are optimized to >>> behave as closely as possible to real objects that are being faked. >>> this means that stubs maintain state for properties for example >>> (PropertyBehaviour). >>> >>> On Oct 20, 5:20 pm, "Tim Barcz" <[EMAIL PROTECTED]> wrote: >>> > I'm familiar with the fowler article and mocking in general...I'm >>> talking in >>> > terms of Rhino.... >>> > >>> > On Mon, Oct 20, 2008 at 8:50 AM, Shane Courtrille < >>> [EMAIL PROTECTED] >>> > >>> > > wrote: >>> > > I'd recommend you start here... >>> > >>> > >http://martinfowler.com/articles/mocksArentStubs.html >>> > >>> > > On Mon, Oct 20, 2008 at 6:09 AM, Tim Barcz <[EMAIL PROTECTED]> >>> wrote: >>> > >>> > >> Am working on a code camp presentation and am trying to distill the >>> > >> subject of mocking with Rhino down to the easiest possible concepts >>> I can >>> > >> think of. >>> > >>> > >> Would you say the following statement is true or false? >>> > >>> > >> Mocks and stubs are the same, except that you can put an expectation >>> on a >>> > >> mock. >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
