February 2018
Intermediate to advanced
406 pages
9h 52m
English
There are a lot of different, sometimes conflicting, goals for tests. It’s hard to know where to start your TDD process, how many tests to write, and when you’re done. The classic description of the process—“write a simple test, make it pass, then refactor”—doesn’t provide a lot of affirmative guidance or direction for the larger process of adding a feature.
The following diagram illustrates a metaprocess that reflects how I write a new business-logic feature. (I handle view logic a little differently.) This process is more of a guideline than a hard-and-fast checklist. As the logic gets more complex, and the less I know about the implementation when I start, the closer ...