testingReflections.com - Mock Objects

Java mocking without dependency injection

Sat, 16 Sep 2006 18:42:29 -0500

Interesting article about using bytecode manipulation to mock dependencies.

Mocha - a new twist on mocking in Ruby

Fri, 01 Sep 2006 13:02:37 -0500

Mocha is a library for mocking and stubbing within tests using a syntax like that of JMock and SchMock. The main difference between this mocking library and others like FlexMock and RSpec is that it allows you to mock and stub methods on real (non-mock) classes and instances.

Rhino.Mocks v. 2.0 Announced. Yes, it's a Mock Object Framework.

Mon, 04 Jul 2005 00:56:34 -0500

Ayende has announced that he's released Rhino.Mocks v. 2.0: his own version of what he'd like in a Mock Object framework. I haven't yet got a chance to try it out, but it certainly sounds interesting!

"Rhino.Mocks is an attempt to create easier way to build and use mock objects and allow better refactoring support from the current tools. It's a hybrid approach between the pure Record/Replay of EasyMock.Net's model and NMock's expectation based model. Rhino.Mocks originated from EasyMock.Net and attempt to improve on their model to create easy to use and power mocking framework. It's free for use and modification for free and commercial software.

The Mock Objects elevator speech

Mon, 04 Jul 2005 00:57:30 -0500

A friend asked me by email the other day :"So why do I need mock objects?" I came up with this in roughly 3 minutes so it's a bit rough, but it'll do to drive the point home, I hope. Note, that this does not really explain the *technical* side of it too much. Just the logic behind the concept. Mock objects are there for when you need to replace or remove dependencies from code under test. Let's say you have a class that manages user logins. Whenever a user login fails the class needs to report to a logger class, or maybe even an email class, or some remote web service to authenticate. If you want to write a test for the logic in the login class (an tests are just methods that call methods on the tested class, really) you want your test to run fast, and to run easily without too much fussing and configuration so that you can get fast feedback.

Schmock: Ruby mock library

Wed, 29 Jun 2005 05:57:35 -0500

Simple mock object implementation knocked together while developing a Ruby on Rails app. Draws from the jmock stable of mocking.

Python Mock Library: mock objects for Python

Sun, 26 Jun 2005 13:21:47 -0500

Mock object library for Python. This library enables the easy creation and use of Mock objects for Python unit testing. The Mock objects can contain expectations about how they are used, and can validate themselves against the class being mocked.

Rhino Mocks: .NET mocking framework

Sun, 26 Jun 2005 13:22:27 -0500

A dynamic mock object framework for the .Net platform. Its purpose is to ease testing by allowing the developer to create mock implementations of custom objects and verify the interactions using unit testing. Rhino.Mocks is an attempt to create easier way to build and use mock objects and allow better refactoring support from the current tools. It's a hybrid approach between the pure R

FlexMock: mock objects for Ruby

Sun, 12 Jun 2005 09:59:58 -0500

FlexMock is a simple mock object for unit testing in Ruby. The interface is simple, but still provides a good bit of flexibility.

Setting Up VirtualMock in the Eclipse IDE

Sat, 23 Apr 2005 11:59:27 -0500

One of the things I teach as part of Team Agile is how to do Test Driven Development and write unit tests in Java. Yes. This is .NET weblogs, but the following information is so scarce and hard to find I just have to post it. After a long time of trial and error trying to run a framework called "VirtualMock" (which is similar to TypeMock in .NET in its purposes). Anyway - it's impossible to figure out how to make the thing work under Eclipse - no documentation found on the net for this. Luckily, Eli Lopian of Amdocs finally found a way to make it work with the Eclipse IDE. He was kind enough to let me post the steps he used to make this happen so that future generations could use this practically non-existent documentation as they search it via Google: Hi, Here are the instuctions for setting up using virtual mock in eclipse. A.1. Setting Up VirtualMocks in eclipse Following is the method to set up virtual mocks in eclipse (3.0). 1. Install AJDT (The AspectJ Development Tool) and restart eclipse.

Mock Objects for C++ 1.5.0 available

Wed, 09 Mar 2005 15:23:16 -0600

[textile]"mockpp":http://mockpp.sourceforge.net/index-en.html is a platform independent unit testing framework for C++. Its goal is to facilitate developing unit tests in the spirit of "Mock Objects for Java" and jMock.

MockCreator: Java Mock Generator

Thu, 17 Feb 2005 00:57:57 -0600

When tests multiply, they often become too complex to support, since minor changes in code often require to alter a bunch of unit tests. MockCreator's special features (such as Dummy, Blocks and Accepts) are targeted to writing test code that knows as little as possible about the actual implementation, testing only logic.MockCreator is in use in large projects, featuring thousands of tests, and it helps users to reduce the pain of test maintenance.

How Mock Objects Happened

Fri, 04 Feb 2005 04:45:08 -0600

Mock Objects is a development technique that lets you unit test classes that you didn't think you could and helps you write better code whilst doing so. This article uses a simple example to show a compressed history of how the Mock Objects technique was discovered by refactoring from conventional unit tests, and what its advantages are.Author: Steve Freeman

SnapDAL: data access layer for .NET code

Fri, 17 Dec 2004 00:29:54 -0600

SnapDAL is a data access layer (DAL) for your .net code. It is designed to make programming against databases and other sources of data easier, with less code, and higher reliability than you could do on your own without lots of discipline. SnapDAL is built with the idea of helping you write testable data access code by support Mock Objects natively as a first class development tool.

I changed my mind - Mock objects are wrong for database unit testing

Sun, 12 Dec 2004 02:54:17 -0600

More than a year ago I wrote about the problems in database testing. I also stated that I feel it's totally wrong to run your unit tests against a live test database, but instead you should be using mock objects to save you from all the trouble. Boy have things changed since then. I take back what I said. For a long time now I've been doing DB testing without mock objects, because I believe that's currently the best way to make sure you test data access logic and integration with the database procedures and views.

Unit Testing with Mock Objects

Sun, 12 Dec 2004 02:56:42 -0600

Recently on a medium-sized project I did a lot of work developing unit tests using the 'Mock Objects' pattern. Whilst I had used this pattern before, this was the largest piece of work to-date. In doing so I learnt a lot about unit testing and believe I went to the very limit of what can be tested.This page and its children talk about unit testing with the Mock Objects pattern. In particular, it covers what Mock Objects are, what tools I have used, and important lessons I have learnt along the way.