CheckArguments question

Hi Tim,

Just wanted to let you know I'll look into this and get back to you shortly.

Doron,
Typemock Support

Tim,
When c# encounters a params argument it is really taking all the arguments, packing them up in an array and passing the array.
So calling

target.Log.LogMessage(string.Empty, path, arguments);

is really calling

object[] temp = new object[] {path, arguments};
target.Log.LogMessage(string.Empty, temp);

once we understand this it is easy to fix the code:

using (RecordExpectations r = new RecordExpectations())
{
     target.Log.LogMessage(null); // arguments ignored
     r.CheckArguments( Check.IsAny(), new object[] {path, arguments} );
}

Tim,
When c# encounters a params argument it is really taking all the arguments, packing them up in an array ...

Thanx, I'll give it shot when I have a chance...

Tim,

There's another option to accomplish the same thing using the Natural Mocks syntax. Natural Mocks support checking the arguments passed to a method by calling CheckArguments() after the call with no parameters:

using (RecordExpectations rec = RecorderManager.StartRecording())
{
     target.Log.LogMessage(string.Empty, path, arguments); 
     rec.CheckArguments();
}

This way we set an expectation against the same arguments passed in the last recorded call. By providing parameters to CheckArguments() you override this mechanism, and in order to check a variable number of arguments you will need to pack them in an object[], like in Eli's example.

I hope this clears things up. Please let us know if this helped.

Doron,
Typemock Support