| Program |
 |
|
|
|
| Find in Program |
|
|
|
|
| Page |
|
|
|
|
| Basket |
|
|
|
|
|
|
Mock Roles, not Objects
Meeting Rooms 11-12
Tuesday, 11:00, 30 minutes | 7 | · | 8 | · | 9 | · | 10 | · | 11 | · | 12 | · | 13 | · | 14 | · | 15 | · | 16 | · | 17 | · | 18 | · | 19 | · | 20 | · | 21 |
Steve Freeman, ThoughtWorks
Tim Mackinnon, ThoughtWorks
Nat Pryce, ThoughtWorks
Joe Walnes, ThoughtWorks
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.
Test-Driven Development, Mock Objects, Java
|
