Test-Driven Development By Example

Introduction

From the mantra of Test-Driven Development: writing failed tests before writing codes, and eliminating duplication, the three-step rule is put forth:

• Write a test at first
• Correct the code to make the test work
• Refactor

Why test-driven development?

Where test-driven development not primarily viable?

• Security
• Concurrency
• User interface

Organization of the book:

1. Examples of test-driven programming
2. Examples of more complicated programming
3. Design patterns