Book Image

Agile Technical Practices Distilled

By : Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia
Book Image

Agile Technical Practices Distilled

By: Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia

Overview of this book

The number of popular technical practices has grown exponentially in the last few years. Learning the common fundamental software development practices can help you become a better programmer. This book uses the term Agile as a wide umbrella and covers Agile principles and practices, as well as most methodologies associated with it. You’ll begin by discovering how driver-navigator, chess clock, and other techniques used in the pair programming approach introduce discipline while writing code. You’ll then learn to safely change the design of your code using refactoring. While learning these techniques, you’ll also explore various best practices to write efficient tests. The concluding chapters of the book delve deep into the SOLID principles - the five design principles that you can use to make your software more understandable, flexible and maintainable. By the end of the book, you will have discovered new ideas for improving your software design skills, the relationship within your team, and the way your business works.
Table of Contents (31 chapters)
Free Chapter
Section 1
Section 2
Section 3
Section 4
Chapter 21
License: CyberDojo

Double Loop TDD

Double loop TDD introduces the concept of acceptance tests in the Red -> Green -> Refactor classic TDD loop. The idea is to have a high-level test that covers a business requirement. As the name implies, we add a second loop to our TDD loop. This is an outer loop and also has Red -> Green -> Refactor stages. In this acceptance test, with the outside loop, we are effectively creating an executable definition of "done."

Figure 16.3: Double loop TDD

When starting a new feature, we begin by writing an acceptance test. This test will inevitably fail since we are lacking an implementation. Before we move on, we need to make sure our acceptance test is failing because it doesn't meet the acceptance criteria. This usually forces us to define the external API of our system.

Once we have a failing acceptance test, we move to the inner loop and stay on it until the acceptance test becomes green. The inner loop corresponds...