List of Figures

Chapter 1: Introduction

Figure 1.1: Class diagram of the dictionary.

Chapter 2: Automating Unit Tests

Figure 2.1: The AWT test runner.

Figure 2.2: The Swing test runner.

Figure 2.3: StringBufferTest without tests.

Figure 2.4: Test runner reports a failure.

Chapter 3: Basic Steps of the Test-First Approach

Figure 3.1: Top-down versus bottom-up approaches.

Figure 3.2: A small test class hierarchy.

Figure 3.3: Package structure with test classes.

Chapter 5: The Inner Life of a Test Framework

Figure 5.1: JUnit class diagram.

Figure 5.2: Sequence diagram for the start of a test case.

Chapter 6: Dummy and Mock Objects for Independence

Figure 6.1: Schematic view of the Dependency Inversion Principle.

Figure 6.2: Schematic view of the mock objects hierarchy.

Chapter 7: Inheritance and Polymorphism

Figure 7.1: A simple inheritance hierarchy.

Figure 7.2: A parallel test hierarchy.

Figure 7.3: Interfaces.

Figure 7.4: Interface test classes.

Chapter 9: Persistent Objects

Figure 9.1: Object model of the CRM application.

Figure 9.2: An object-centered persistence interface.

Chapter 12: Web Applications

Figure 12.1: MyServlet in the browser.

Figure 12.2: Test case running in Cactus.

Figure 12.3: ServletInvocation.

Chapter 13: Graphical User Interfaces

Figure 13.1: The desired Product Editor layout.

Figure 13.2: A "rudimentary" layout.

Figure 13.3: The improved layout.

Chapter 14: The Role of Unit Tests in the Software Process

Figure 14.1: Activities, intermediate results, and products in the development process.

Figure 14.2: Quality-assurance tasks.

Figure 14.3: The waterfall model [Boehm76].

Figure 14.4: An incremental process.

Figure 14.5: Comparing the costs of manual versus automated testing.

Figure 14.6: Structure of the Rational Unified Process.

Figure 14.7: Relations between the RUP's testing artifacts.

Appendix B: Unit Tests with Other Programming Languages

Figure B.1: The SUnit test runner.

Figure B.2: A graphical test runner.