Comments on: Mocking .NET Objects with NUnit

By: Mocking With NUnit « bloggersfun

Mocking With NUnit « bloggersfun — Fri, 26 Sep 2008 03:03:20 +0000

[...] Mocking With NUnit If you choose Nunit for you Unit Testing and with Mock object for isolating classes from their dependencies for testing purposes.You can go through this tutorial:http://www.zorched.net/2007/03/10/mocking-net-objects-with-nunit/ [...]

By: Deva

Deva — Wed, 02 Jul 2008 11:18:04 +0000

Hi,
Do you have a documentation for the NMock Example Project given

By: Dave Paulino

Dave Paulino — Wed, 02 Jul 2008 03:23:17 +0000

@Chad
Very good article and very well explained. This will help developers to understand mock object.

@Geoff
Using the scenario above I agree it is very hard to unit test, but we can use to MVP design pattern to unit test our code.

By: Geoff Lane

Geoff Lane — Thu, 22 May 2008 14:15:58 +0000

Chad,
In a Real application the Service would likely implement an Interface as well. You could then call the Service from UI code. Using ASP.NET, you would likely need to use a framework like Spring .NET to wire together your dependencies. If you do that though, you can then inject those dependencies into your Pages.


public class ViewPerson : Page {
    private IPersonService personService;
    protected void Page_Load(object sender, EventArgs e)
    {
        Person person = personService.GetPerson(Request.QueryString["personId"]);
        // ... do something with person
    }
}

That doesn’t necessarily help a lot with Unit Testing though. Web/UI code is hard to unit test. Your best bet is to keep your UIs very thin, with very little code, and use it merely as a translation layer to get things out of the Web context and into “plain code” context. Then you can Unit Test all of the other code and leave testing of UIs to functional tests.

By: Chad

Chad — Thu, 22 May 2008 04:00:04 +0000

Hi Geoff

Im wading my way through loose coupling using interfaces. Forcing me to think about my dependencis before I code. What would be a quick example of your classes using asp.net as a GUI using the above example?

Regards
Chad

By: Geoff Lane

Geoff Lane — Fri, 29 Feb 2008 02:31:51 +0000

Christopher,
Was that an ArgumentException? Using this technique and NMock you can only mock things based on an Interface, not a concrete types. Using an interface is a good practice anyway because it leads to a looser coupling of your objects.

If your really must mock concrete classes (you want to give up loose coupling, or are dealing with dependencies that were not written by you), you might want to look at another Mocking framework like Rhino Mocks.

Hope that helps.

By: Christopher Piggott

Christopher Piggott — Fri, 29 Feb 2008 02:14:21 +0000

I tried the above example using my own classes, but I get this:

at System.Runtime.Remoting.Proxies.RealProxy..ctor(Type classToProxy, IntPtr stub, Object stubData)
at NUnit.Mocks.DynamicMock.get_MockInstance()
at SerialWidgetTest_Test.SSHStreamTest.Test1() in C:\WORK\firmware\Helpers\C#\trunk\TestWidgets\TestWidget_NUnit\SSHStreamTest.cs:line 27

I’m not even sure what that means. Is the type of object I’m trying to mock too complex?

By: hitesh

hitesh — Tue, 15 Jan 2008 16:09:38 +0000

Very good sample…it helps me to understand the creation of mock object and use them for unit testing