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

Different Types of Test Doubles

Dummy Objects

Dummy objects are needed only to complete the parameters' list of a method but are never actually used. They are not very common in well-designed systems since they are often an indication of room for design improvements.


Stubs respond to calls made during a test with some pre-programmed output specific for each test. This implies that they need to be specifically set up for every test.

Stubs are used to provide synthetic replacements for queries called on collaborators of the Subject Under Test.

Fake Objects

Fake objects are handmade stubs (sometimes called poor man Stubs).


Mocks are set up with expectations of the calls they are expected to receive. They can throw an exception if they receive a call they don't expect and/or are queried during the assertion phase to verify that they received all the calls they were expecting.

Mocks are used to provide a way of confirming that commands have...