Skip to main content

RhinoMocks: execute a specific action when a method is called

When writing unit tests sooner or later you are confronted with mocking. I always try to keep my mocking code as simple as possible. Sometimes this means creating a mock object manually and sometimes it means using a mocking framework. The mocking framework I use the most is RhinoMocks created by Ayende Rahien.

Last week I had to mock a call to a specific method and execute some code when this method is called to test some specific behavior. Creating a mock object myself for this would be rather cumbersome, with Rhinomocks this becomes really simple:

   1:  var repository=MockRepository.GenerateMock<IDeliveryRepository>();
   2:  repository.Expect(rep => rep.ReadDeliveryData(null, null))
   3:                        .IgnoreArguments()
   4:                        .Do(new Action(()=>task.Process(data, delivery)));
   5:   

It’s important that the code you execute in the Do() matches the signature of the method that is called in the Expect(). The first time I implemented this the test failed with the following error message:

“Callback arguments didn't match the method arguments.”

because the code I executed in the Do() didn’t match.

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...