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

Organizing Your Test in Arrange, Act, and Assert Blocks

Tests are about assertions (ASSERT). For an assertion to be possible, we need to take an action on the code we are asserting (ACT). Sometimes, to take an action, we need to create the context to enable the action (ARRANGE). Organizing tests in arrange, act, and assert blocks helps keep the tests clean and easy to read.

For example, let's look at fizzbuzz:

    //Arrange block (aka Given) – create all necessary preconditions
    var fizzBuzzer = new FizzBuzzer()
    //Act block (aka When) – execute the subject under test
    var fizzBuzzed = fizzBuzzer.FizzBuzz(1)
    //Assert block (aka Then) – assert the expected results have occurred
    assert fizzBuzzed == "1"

However, we think that less is more when we are trying to understand the meaning of some code. We are not...