recordExpectations.ExpectAndReturn() question

Nice one :oops:

This is a scenario that we missed, (returning arrays.)
We will send you a fix offline.

By the way, the code can be must simpler using the following:

using (RecordExpectations recordExpectations = RecorderManager.StartRecording())
{
....
    EventBase[] eventBases = new EventBase[]{new EventBase()};
    recordExpectations.ExpectAndReturn(
       EventFactory.Instance.GetEvents(), eventBases);            
....
}

This will work after the patch we will send

Thanks Scott - the patch fix worked with the code you suggested. 8)

However, it still generated a different error on a following line using the eventBases as an expected arg:

using (RecordExpectations recordExpectations = RecorderManager.StartRecording())
{
    recordExpectations.ExpectAndReturn(EventFactory.Instance.GetEvents(), eventBases);

    mockVFrameworkEventManager.ExpectCall("RegisterEvents").Args(eventBases);
}

The 'RegisterEvents' expectation fails as follows:

TypeMock.VerifyException : 
TypeMock Verification: Call to Rbsfm.Rates.VFramework.VFrameworkEventManager.RegisterEvents() Parameter: 1
    expected: <"Event - :" [Rbsfm.Rates.VFramework.Events.EventBase]>
     but was: [Rbsfm.Rates.VFramework.Events.EventBase[]]

I was able to fix this by changing the expectation to :

mockVFrameworkEventManager.ExpectCall("RegisterEvents").Args(new object[]{eventBases});

:idea: I know that Args uses a param argument and so I assume that each element in the array passed is treated as a separate argument to verify causing the fail - maybe this should be detailed in the guide that if passing an array as an expected arg it needs to be bounded in an object array?

Thanks again.

Hi,
Your observation is correct.
I will ask to put this in our documentation.

:idea: version 3.5.1 now handles passing a single array as an expected arg automatically and there is no needs to bound the array in an object array.

Thanks for pointing this out.