I just re-read
MocksArentStubs.
David Spades wrote: and therefore if you use mock, you're definitely using BDD instead of TDD. Is this about right?
No. In fact the article even gives an example of TDD for mocks.
A mockist TDD practitioner, however, will always use a mock for any object with interesting behavior. In this case for both the warehouse and the mail service.
David Spades wrote: I also get the impression that stubs are becoming obsolette since more and more people are shifting to mocks (the "there's nothing that mocks can't do but stub can" argument). thanks
Libraries like
jMock let you write stubs so people often think of them as mocks regardless of what they really are.