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

Acceptance Tests Done Right

An Acceptance Test suite must have well-defined properties in order to provide benefits. It is important to set goals early on so we can always have a clear idea of what we want to achieve and make trade-off decisions based on those goals.

Readable by Business Folks

In this context, the expressivity of the four elements of simple design have a key role. If it is not possible to sit with an analyst or a product owner in front of the acceptance criteria to have the discussion mentioned earlier, we have a clear red alarm signal. It means that the "glue" with the business is not working properly, and the risk is very high that we'll end up with acceptance tests that are ineffective and/or useless.

It is not necessary to use heavyweight frameworks to achieve this as long as we keep the scenario specifications well sorted and separate from the implementation. Businesspeople are not intimidated if we use an underscore instead of a blank...