jMock: supporting responsibility-based design with mock objects

Authors:
Steve Freeman;Tim Mackinnon;Nat Pryce;Joe Walnes
Affiliations:
ThoughtWorks UK, High Holborn, London;ThoughtWorks UK, High Holborn, London;ThoughtWorks UK, High Holborn, London;ThoughtWorks UK, High Holborn, London
Venue:
OOPSLA '04 Companion to the 19th annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applications
Year:
2004

Citing 3
Cited 3

A laboratory for teaching object oriented thinking

OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
Refactoring: improving the design of existing code

Refactoring: improving the design of existing code
Test Driven development: A Practical Guide

Test Driven development: A Practical Guide

Application of automated environment generation to commercial software

Proceedings of the 2006 international symposium on Software testing and analysis
Embedded typesafe domain specific languages for Java

Proceedings of the 6th international symposium on Principles and practice of programming in Java
On designing safe and flexible embedded DSLs with Java 5

Science of Computer Programming

Quantified Score

Hi-index	0.01

Visualization

Abstract

In this demonstration we will show the flow of the Mock Object development process by pair-programming to develop a code example. During the session, we will introduce the declarative jMock API and show how we use it to describe relationships between objects when developing test-first. We will show how this approach helps developers concentrate on real requirements and how it encourages a design in which objects are focused with well-defined responsibilities. We will also show our practices for maintaining the readability of tests written using jUnit with jMock. This work is described in a Practitioner Report at this conference, "Mock Roles, Not Objects".