Mock roles, 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

Quantified Score

Hi-index 0.00

Visualization

Abstract

Mock Objects is an extension to Test-Driven Development that supports good Object-Oriented design by guiding the discovery of a coherent system of types within a code base. It turns out to be less interesting as a technique for isolating tests from third-party libraries than is widely thought. This paper describes the process of using Mock Objects with an extended example and reports best and worst practices gained from experience of applying the process. It also introduces jMock, a Java framework that embodies our collective experience.