Understanding Mock and frameworks – Part 4 of N

By · 2 Comments

I am glad that this series has been liked by large audience and even got focus on Channel9 Video and that motivates to continue this series further on.

This series on Mock and frameworks takes you through Rhino Mocks, Moq and NSubstitute frameworks to implement mock and unit testing in your application.  This series of posts is full of examples, code and illustrations to make it easier to follow.  If you have not followed this series through, I would recommend you to read following articles

  1. Understanding Mock and frameworks – Part 1 of N – Understanding the need of TDD, Mock and getting your application Unit Test ready
  2. Understanding Mock and frameworks – Part 2 of N – Understanding Mock Stages & Frameworks – Rhino Mocks, NSubstitute and Moq
  3. Understanding Mock and frameworks – Part 3 of N -  Understanding how to Mock Methods calls and their Output – Rhino Mocks, NSubstitute and Moq

This part of the series will focus on exception management, and subscribing to events

Exception Management

 

Going back to the second post where we defined our Controller and Service interface,  the method GetObject throws an ArgumentNullException when a NULL value is passed to it.  The Exception Management with Mock allows you to change the exception type and hence, ignore the exception peacefully.

Using Rhino Mocks

Using the Stub method of Mocked Service, you can override the exception type.  So instead of getting a ArgumentNullException, we will change the exception to InvalidDataException.  But do not forget to add a ExceptedException attribute to the method (line 2 in example below) that ensures a peaceful exit.

  1. [TestMethod]
  2. [ExpectedException(typeof(InvalidDataException))]
  3. publicvoid T05_TestExceptions()
  4. {
  5.     var service = MockRepository.GenerateMock<IService>();
  6.     // we are expecting that service will throw NULL exception, when null is passed
  7.     service.Stub(x => x.GetObject(null)).Throw(newInvalidDataException());
  9.     Assert.IsNull(service.GetObject(null)); // throws an exception
  10. }

Using NSubstitute

NSubstitute does not expose a separate /special function like Throw. It treats exceptions as a return value of the test method. So u

  1. [TestMethod]
  2. [ExpectedException(typeof(InvalidDataException))]
  3. publicvoid T05_TestExceptions()
  4. {
  5.     var service = Substitute.For<IService>();
  6.     // we are expecting that service will throw NULL exception, when null is passed
  7.     service.GetObject(null).Returns(args => { thrownewInvalidDataException(); });
  9.     Assert.IsNull(service.GetObject(null)); // throws an exception
  10. }

Using Moq

Moq exposes Throws method just like Rhino Mocks

  1. [TestMethod]
  2. [ExpectedException(typeof(InvalidDataException))]
  3. publicvoid T05_TestExceptions()
  4. {
  5.     var service = newMock<IService>();
  6.     // we are expecting that service will throw NULL exception, when null is passed
  7.     service.Setup(x => x.GetObject(null)).Throws(newInvalidDataException());
  9.     Assert.IsNull(service.Object.GetObject(null)); // throws an exception
  10. }

Event Subscriptions

The next topic of interest in this series is managing Event Subscriptions with Mock frameworks. So the target here is to check if an event was called when some methods were called on the mocked object

Using Rhino Mocks

The code here is little complex compared to all previous examples.  So we are adding a ServiceObject to the controller which raises an event. Unlike real time examples, this event is hooked to the DataChanged method of the service. This means the controller will raise an event and a service method will be called dynamically.

  1. [TestMethod]
  2. publicvoid T06_TestSubscribingEvents()
  3. {
  4.     var service = MockRepository.GenerateMock<IService>();
  5.     var controller = newController(service);
  7.     controller.CEvent += service.DataChanged;
  8.     ServiceObject input =newServiceObject(“n1″, Guid.NewGuid());
  9.     controller.Add(input);
  11.     service.AssertWasCalled(x => x.DataChanged(Arg<Controller>.Is.Equal(controller),
  12.         Arg<ChangedEventArgs>.Matches(m=> m.Action == Action.Add &&
  13.                                               m.Data == input)));
  14. }

Let’s go into detail of the AssertWasCalled statement – it takes a method handler in the lambda expression. Some of the other methods of interest are Arg<T> Is.Equal and Matches. The method Arg<T> creates a fake argument object of a particular type. Is.Equal() method assigns a value to it and Matches method adds like a filter on the values of input parameters to the original ‘DataChanged’ method.

Using NSubstitute

NSubstitute has a different set of methods for event subscription.  The output of Received() method exposes all valid method calls available, Arg.Is<T>() creates fake object for mocked service.

  1. [TestMethod]
  2. publicvoid T06_TestSubscribingEvents()
  3. {
  4.     var service = Substitute.For<IService>();
  5.     var controller = newController(service);
  7.     controller.CEvent += service.DataChanged;
  8.     ServiceObject input = newServiceObject(“n1″, Guid.NewGuid());
  9.     controller.Add(input);
  11.     service.Received().DataChanged(controller,
  12.       Arg.Is<ChangedEventArgs>(m => m.Action == Action.Add && m.Data == input));
  13. }

Using Moq

Apart from having different names of methods from NSubstitute, Moq does exactly the same as other two frameworks

  1. publicvoid T06_TestSubscribingEvents()
  2. {
  3.     var service = newMock<IService>();
  4.     var controller = newController(service.Object);
  6.     controller.CEvent += service.Object.DataChanged;
  7.     ServiceObject input = newServiceObject(“n1″, Guid.NewGuid());
  8.     controller.Add(input);
  10.     service.Verify(x => x.DataChanged(controller,
  11.         It.Is<ChangedEventArgs>(m => m.Action == Action.Add && m.Data == input)));
  12. }

The Code for Download

Understanding RhinoMocks, NSubstitute, Moq by Punit Ganshani

So that concludes how to use Rhino Mocks, NSubstitute and Moq for Exception Handling and Event Subscriptions.  Should you have any questions, feel free to comment on this post.

Punit Ganshani

Punit Ganshani, based out of Singapore, specializes in Microsoft technology stack and performance engineering. He is an open-source contributor at Codeplex, has several apps on Windows Phone Store and is a noted speaker on Performance Tuning, Mobile Development and Application Design

More Posts - Website

Follow Me:
TwitterFacebookLinkedInGoogle PlusReddit

Related posts:

  1. Understanding Mock and frameworks – Part 3 of N This series on Mock frameworks takes you through Rhino Mocks,...
  2. Understanding Mock and frameworks – Part 2 of N Continuing on where we left in the previous post –...
  3. Understanding Mock and frameworks – Part 1 of N We have several posts on the Internet that focus on...
  4. Intercepting method calls using IL Interception – The word interception is heard more in Canadian...
Tagged with: • • • • • • • •
 
If you enjoyed this article, please consider sharing it!
Reddit Facebook Twitter Delicious Mixx StumbleUpon Digg

2 Responses to Understanding Mock and frameworks – Part 4 of N

  1. Understanding Mock and frameworks - Part 3 of N says:
    January 26, 2013 at 3:21 pm

    [...] this helps. In the next post, we will explore how to mock Exceptions and [...]

  2. RhinoMocks, NSubstitute and Moq – Punit Ganshani says:
    February 13, 2013 at 8:27 pm

    [...] Understanding Mock and frameworks – Part 4 of N -  Understanding how to Mock Exceptions and Event Subscriptions  – Rhino Mocks, NSubstitute and Moq [...]

%d bloggers like this: