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

Golden Master

The Golden Master technique is very useful when a clear input and output is easy to obtain on the system level. There are some cases where the Golden Master technique can be applied only with difficulty or where it cannot be applied at all. For all the given situations, we need to consider whether the system tests generated with the Golden Master are enough, or whether we need to add other types of tests such as unit tests, component tests, integration tests, and so on.

In the following subsections, we provide guidelines to create a Golden Master for a system.


  1. Does the system have clear inputs and outputs? Examples may include the console, filesystem, network, and so on.
  2. Does the system generate the same output for the same input? If not, can we use a test double to make it so? Isolate the side effects.
  3. Can we capture the effect of the system on our tests without changing the behavior of the system? The options are to either redirect...