Modern C++ Programming with Test-Driven Development

10.4 The Transformation Priority Premise

Throughout the book, I’ve suggested that the next test you write is the one that grows your system by the smallest increment. If you strictly adhere to the TDD cycle, seeking to always demonstrate test failure before you move on, you will learn what it means to take too large a step. (See Section 3.5, ​Getting Green on Red​.) Following the last rule of simple design—minimize the total number of classes and methods (see Section 6.2, ​Simple Design​)—will also help by teaching you to avoid overdesigning your system and putting more code in place than need be. The third rule of TDD (Section 3.4, ​The Three Rules of TDD​) also tells you to put no more code in place than necessary to pass your tests.

Small ...