I am trying to use Moq to write a unit test. Here is my unit test code:
var sender = new Mock<ICommandSender>();
sender.Setup(m => m.SendCommand(It.IsAny<MyCommand>(), false))
.Callback(delegate(object o)
{
var msg = o as MyCommand;
Assert.AreEqual(cmd.Id, msg.Id);
Assert.AreEqual(cmd.Name, msg.Name);
})
.Verifiable();
SendCommand
takes an object and optional boolean parameter. And MyCommand derives from ICommand.
void SendCommand(ICommand commands, bool idFromContent = false);
When the test runs, I see the error
System.ArgumentException : Invalid callback. Setup on method with parameters (ICommand,Boolean) cannot invoke callback with parameters (Object).
I want to check if the content of the message is what I sent in. I searched the forum and found a couple of different variations of this issue, but those didn't help. Any help is greatly appreciated.
You need to call the generic overload of Callback with the specific types expected by the method. The following should work:
sender.Setup(x => x.SendCommand(It.IsAny<MyCommand>(), false))
.Callback<ICommand, bool>((command, idFromContent) =>
{
var myCommand = command as MyCommand;
Assert.That(myCommand, Is.Not.Null);
Assert.That(myCommand.Id, Is.EqualTo(cmd.Id));
Assert.That(myCommand.Name, Is.EqualTo(cmd.Name));
})
.Verifiable();
If the assertions fail in the callback then the test fails immediately, so the call to Verifiable() (and presumably the subsequent call to Verify()) seems to be redundant. If you want to allow the mocked Send invocation to proceed even if it does not meet the criteria and then verify it after the fact, then you can do this instead (after the tested method is invoked):
sender.Verify(x => x.SendCommand(It.Is<MyCommand>(c =>
{
Assert.That(c, Is.Not.Null);
Assert.That(c.Id, Is.EqualTo(cmd.Id));
Assert.That(c.Name, Is.EqualTo(cmd.Name));
return true;
}), false), Times.Once());
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With