Invalid call, the last call has been used or no call has been made

Question

I am getting this error when I try to set a mock to have PropertyBehavior():

System.InvalidOperationException: System.InvalidOperationException: Invalid call, the last call has been used or no call has been made (make sure that you are calling a virtual (C#) / Overridable (VB) method)..

I am trying to use only Rhino Mocks 3.5 (Arrange, Act, Assert)

Here is my code:

    private IAddAddressForm form;

    private AddAddressMediator mediator;

    [TestInitialize()]
    public void MyTestInitialize()
    {
        form = MockRepository.GenerateMock<IAddAddressForm>();
        mediator = new AddAddressMediator(form);


        // Make the properties work like a normal property
        Expect.Call(form.OKButtonEnabled).PropertyBehavior();

        //I tried this too.  I still get the exception
        //SetupResult.For(form.OKButtonEnabled).PropertyBehavior();
    }


    [TestMethod]
    public void TestOKButtonEnabled()
    {

        form.OKButtonEnabled = true;
        Assert.IsTrue(form.OKButtonEnabled);
    }

I know I could use a stub (and for the code above I should) but I am trying to learn Rhino Mocks.

Eventually I want to be able to make sure that several properties has their values accessed. (Any hints on how to check that form.FirstName was accessed (i.e. the getter was called) would also be appreciated.)

In case it is needed, here is the code to IAddressForm:

namespace AddressBook
{
    public interface IAddAddressForm
    {
        string FirstName { get; set; }
        string LastName { get; set; }
        string Address1 { get; set; }
        string State { get; set; }
        string Address2 { get; set; }
        string ZipCode { get; set; }
        string City { get; set; }
        bool OKButtonEnabled { get; set; }
    }
}

Anyway, I thought that virtual would not be a problem as I am passing in an interface, but I am clearly missing something.

Answer 1

Never used PropertyBehavior before, but is this the syntax you're looking for?

form.Stub(x=>x.OKButtonEnabled).PropertyBehavior()

Rhino Mocks works completely through extension methods now. The only static call I every make any more is to MockRepository.GenerateStub.

Answer 2

You mentioned using a stub instead of a mock but before you go changing it I'd note that strangely, I get the Invalid Call exception when I used GenerateStub but not when I use GenerateMock.

View = MockRepository.GenerateStub<IAddressView>();
View.Stub(v => v.Message).PropertyBehavior();

This throws the Invalid call exception and yes, IAddressView.Message does have a getter and setter.

Answer 3

I received this error when I tried to set an expectation on a non-virtual method.

mockedObject.Expect(a => a.NonVirtualMethod()).Returns(null);

The error went away when I made NonVirtualMethod virtual.

Answer 4

I think you have to do MockRepository.ReplyAll() after you set up all expectations and before you start using this mock. So my guess in your case is that you have to move the Expect.Call line before mediator = new AddAddressMediator(form);, and stick the reply all right after that:

[TestInitialize()]
public void MyTestInitialize()
{
    form = MockRepository.GenerateMock<IAddAddressForm>();
    // Make the properties work like a normal property
    Expect.Call(form.OKButtonEnabled).PropertyBehavior();

    //I tried this too.  I still get the exception
    //SetupResult.For(form.OKButtonEnabled).PropertyBehavior();

    MockRepository.ReplyAll();
    mediator = new AddAddressMediator(form);



}

Answer 5

I ran into this issue when I was trying to call an internal property (getter only) on an object in C#. In this case, adding .PropertyBehavior() did not help.

My solution was to extract the logic out of the property and into an internal method which I then injected dependencies into this method (as parameters).