[rspec-users] Role of stories vs specs, revisited

[Jay Donnell]

> If you were to rename deposit to credit, and withdraw to debit

I'm more concerned with adding a parameter or changing the default value of a parameter. My fear is that given enough time and size there will be a fair number of inconsistent mocks or mocks that aren't doing any real testing. It feels a bit like forced exception handling in java.

> User stories represent some facet of behavior which, once completed,
> provides value to the customer.  In short, working software.  By
> definition, then, stories must use real production implementations of
> objects instead of mocks.  This means they work quite nicely as
> integration tests as well.


Does anyone know of any open source ruby apps (preferably rails) that use good BDD so I can see how it's done right rather than ask a bunch of questions?



      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ