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
1
Section 1
7
Section 2
13
Section 3
19
Section 4
25
Chapter 21
28
License: CyberDojo

Great Habits

In this lesson, we introduced a new habit. Check it out in the following lists.

Considerations When Writing a New Test

  • Tests should test one thing only.
  • Create more specific tests to drive a more generic solution (triangulate).
  • Give your tests meaningful names (behavior/goal-oriented) that reflect your business domain.
  • See that the test fails for the right reason.
  • Ensure you have meaningful feedback from failing tests.
  • Keep your tests and production code separate.
  • Organize your unit tests to reflect your production code (similar to the project structure).
  • Organize your test into arrange, act, and assert blocks.
  • Write the assertion first and work backward.
  • Write fast, isolated, repeatable, and self-validating tests.
  • Consider using object calisthenics to drive design decisions.
  • Consider adding tests to legacy code.

Considerations When Making a Failing Test Pass

  • Write the simplest code to pass the test...