Geek asks and answers

Rhino Mocks - Do We Really Need Stubs?

If possible, change the behavior layout in Rhino Mocks using mock.Stub (). Return (), why do we need stubs?

What do we lose by always using MockRepository.GenerateMock ()?

One of the great advantages of using Mocks instead of Stubs is that we can reuse the same instance among all the tests so that they are cleaner and more understandable.

The moq structure works in a similar way ... we do not have different objects for mocks and stubs.

(please do not respond with reference to Fowler's article "Poppies are not stubs")

+5
source share
2 answers

, Rhino 1. :

, , " ", , .

, (mock, stub, fake) , Mark Seemann :

, - . , , : ? , , , .

, Rhino , . , stubbing property getter:

var mock = MockRepository.GenerateMock<IService>();
mock.Stub(m => m.Property).Return(42);

, . , Stub , :

var stub = MockRepository.GenerateStub<IService>();
stub.Property = 42;

, , , . , .

1: 05/19/2013, : Rhino Mocks new home >

+6

:

- , , , . - , . , , . , .

, . , , , .

: .

+3

More articles:


All Articles