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

Approval Tests by Llewellyn Falco

Approval Tests is a testing framework conceived by Llewellyn Falco based on the idea of a Golden Master. It has a fluent API that allows for the definition of scenarios and verification of outputs. Typically, it will serialize the output of an execution that the human will mark as accepted. If anything in the code changes the output, the test will fail.

Llewellyn Falco:

A less-known usage for Approval Tests is the locking of code for refactoring. By locking of code, we mean the activity of adding tests around a piece of code to make refactoring possible. Using a code coverage tool in conjunction with this technique provides feedback on how much code has actually been exercised by our new tests. When we reach a satisfactory level of coverage, we can then move to the refactoring phase. Once our code is in better shape and the components are extracted and isolated, they should be easier to understand. We can then add tests...