concept which approach in category software development

This is an excerpt from Manning's book Test Driven: Practical TDD and Acceptance TDD for Java Developers.
As we discussed earlier in the context of breadth-first and depth-first, there is more than one approach to plotting our way towards a full solution. At that time, we decided to keep faking the template parsing logic, effectively postponing the implementation of that part until it was absolutely required. We could’ve decided otherwise just as well. There are no hard and fast rules about which approach to adopt—it’s very much a case-by-case decision. This time, we’ve come to realize that it’s probably better to take the depth-first route, as our Template class is gaining more and more complexity.
There are a few basic concepts related to the unit tests that we write as part of test-driven development that I feel deserve more of our attention than we’ve given them so far. Next, we’re going to fix the situation by discussing the meaning of terms such as fixtures and test doubles. We’ll also highlight two different approaches of verification that we can make use of in our tests. Finally, before taking a closer look into test doubles in section 4.3, we’ll discuss when to use which approach—or whether we can use both.