Recursive mocking with Rhino-Mocks

interfacepropertiesrecursionrhino-mocks

I'm trying to unittest several MVP implementations and can't quite figure out the best way to mock the view. I'll try to boil it down. The view IView consists e.g. of a property of type IControl.

 interface IView
{
    IControl Control1 { get; }
    IControl Control2 { get; }
}

interface IControl
{

    bool Enabled { get; set; }

    object Value { get; set; }

}

My question is whether there's a simple way to setup the property behavior for Enabled and Value on the IControl interface members on the IView interface – like recursive mocking a guess. I would rather not setup expectations for all my properties on the view (quite a few on each view).

Thanks in advance

Best Answer

You will have to set the behavior of each IControl instance separately. You cannot define the behavior on the type level.

If your scenario really is this simple, I would consider making a ValidControl and an InvalidControl that both implement IControl, and just use instances of those instead of mocking IControl with Rhino Mocks. You should probably still mock IView because you don't seem to have a way of setting the controls on the view.

Related Solutions

R – Beginner Rhino Mock problem

You need to mock the View property as well, instead of calling the Init method on the mocked presenter.

presenter.Expect( p => p.View ).Return( view );

You might also want to look at using the new AAA (Arrange-Act-Assert) syntax for RhinoMocks.

string expectedResult = "Done stuff with Mocked Result";

var view = MockRepository.GenerateMock<IView>();
view.Expect( v => v.SomeData ).Return( "Mocked Result" );

var presenter = new Presenter();
presenter.Init( view );

string actualResult = presenter.DoStuff();

Assert.AreEqual( expectedResult, actualResult );

view.VerifyAllExpectations();

EDIT After looking at this again, I would agree with @ayende that you should probably only mock/stub the view not the presenter. I'll leave the original correction to get your code to work, but update my example to reflect the latter.

What are the differences between mocks and stubs on Rhino Mocks

As per this

... Put simply there is a difference between Mock and Stub objects and RhinoMocks recognizes that allowing us to write tests that better state their purpose.

Mock objects are used to define expectations i.e: In this scenario I expect method A() to be called with such and such parameters. Mocks record and verify such expectations.

Stubs, on the other hand have a different purpose: they do not record or verify expectations, but rather allow us to “replace” the behavior, state of the “fake”object in order to utilize a test scenario ...

Best Answer

Related Solutions

R – Beginner Rhino Mock problem

What are the differences between mocks and stubs on Rhino Mocks

Related Topic