http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660So the general case would be to use stubs. Only unit tests that really test for interoperation between the SUT and it's dependencies should use mocks, one at a time. Sounds reasonable, thanks! http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment7http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment7Sat, 28 Jun 2008 16:37:52 GMTStubs are generally more useful than mocks. You should have a single mock object in each your test, no more. The lack of VerifyAll() goes back to needing only a single mock object per test. http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment6http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment6Sat, 28 Jun 2008 16:21:12 GMTHi Oren, First of all, the new syntax looks and feels nice! I have two questions: 1) I noticed that in none of the tests you're setting up any expectations, everything is stubbing only. Is this a coincidence just for these tests or would you generally recommend less mocking (in the sense of setting expectations) and more stubbing? 2) GenerateStub and GenerateMock create a new MockRepository on every call. In the case of mocks with expectations I would need to vall VerifyAllExpectations() on every mock. I actually liked mockRepository.VerifyAll() which won't work with mocks created with GenerateMock. Will there be equivalent instance methods in Rhino Mock 3.5 RMT that do the same as GenerateStub/GenerateMock (ie. call Stub/DynamicMock on the MockRepository and set them in Replay mode directly)? Regards, Andre http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment5http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment5Sat, 28 Jun 2008 11:54:34 GMTThis test doesn't use a database, it is completely in memory one. http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment4http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment4Fri, 13 Jun 2008 14:23:19 GMTAyende, Comparing the test fixture implementation to the one in your article "Answer:How many tests?" shows that you do not inherit from DatabaseTestFixtureBase any more. When is it recommended to inherit from DatabaseTestFixtureBase and why did you choose not to inherit this time? Thanks, Alex http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment3http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment3Fri, 13 Jun 2008 14:00:36 GMTIt's great to see lambda support with Rhino Mocks. I started looking at Moq because of the tight integration with some of the new c# features, and lambda expressions seem to be a very intuitive approach to mocking. Very nice job as always! http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment2http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment2Fri, 13 Jun 2008 11:48:39 GMTthat looks really nice. I'll start playing with it next week. http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment1http://ayende.com/3362/the-test-of-fire-rhino-mocks-3-5-in-the-real-world#comment1Fri, 13 Jun 2008 03:25:54 GMT