Unit Testing with Rhino Mock .Net

What is unit Test?

It is a method of testing a smallest unit of source code. Unit can be function or method. Unit tests are created during development process by developers or occasionally white box testers. Ideally each test case should be independent from each others. Unit tests helps to maintain quality of your application, it helps to find out any error or discrepancy during development process. There are many libraries available to unit test source code like nunit, mbunit, junit, MSTest etc.

What is mock object?

• The mock objects are proxy of real objects which mimic behavior of real objects. Mock objects are mainly used in testing when testing with real objects is impractical or impossible to incorporate in unit testing. Below is some characteristics that can help you to decide to use mock objects.

• Testing data is dynamic i.e. testing results cannot be determine on every test.
• Unit testing includes network or database dependencies.
• You don’t know about behavior of dependent objects.

Mock objects in this sense do a little more: their method implementations contain assertions of their own. This means that a true mock, in this sense, will examine the context of each call— perhaps checking the order in which its methods are called, perhaps performing tests on the data passed into the method calls as arguments.

What is Rhino Mock?

It is a dynamic mock object framework for the .Net platform. It includes features from EasyMock.Net and NMock. Below is some features of this library:

• It can mock interfaces, delegates and classes including parameterized constructors.
• Explicit Record & replay model for expectations.
• Can work for strong type mock objects.
• Expectations are based on
• Argument matching.
• Constraints matching.
• Custom callback to verify the expected arguments using your own code.
• Setting actions of methods, properties to return pre determine value.
• you can also tests methods which doesn’t return any value. In this case you can test interaction based testing ie. you can verify specific sequence of actions and then you can verify these actions according to predefined order.
• State base Testing: initiate action and then check  expected results.

Read more: Beyond Relational

Posted via email from Jasper-net