Book Image

Test-Driven Java Development, Second Edition - Second Edition

By : Viktor Farcic, Alex Garcia
Book Image

Test-Driven Java Development, Second Edition - Second Edition

By: Viktor Farcic, Alex Garcia

Overview of this book

Test-driven development (TDD) is a development approach that relies on a test-first procedure that emphasizes writing a test before writing the necessary code, and then refactoring the code to optimize it.The value of performing TDD with Java, one of the longest established programming languages, is to improve the productivity of programmers and the maintainability and performance of code, and develop a deeper understanding of the language and how to employ it effectively. Starting with the basics of TDD and understanding why its adoption is beneficial, this book will take you from the first steps of TDD with Java until you are confident enough to embrace the practice in your day-to-day routine.You'll be guided through setting up tools, frameworks, and the environment you need, and we will dive right into hands-on exercises with the goal of mastering one practice, tool, or framework at a time. You'll learn about the Red-Green-Refactor procedure, how to write unit tests, and how to use them as executable documentation.With this book, you'll also discover how to design simple and easily maintainable code, work with mocks, utilize behavior-driven development, refactor old legacy code, and release a half-finished feature to production with feature toggles.You will finish this book with a deep understanding of the test-driven development methodology and the confidence to apply it to application programming with Java.
Table of Contents (18 chapters)
Title Page
Packt Upsell
Contributors
Preface
9
Refactoring Legacy Code – Making It Young Again
Index

Summary


Throughout Alice's fictitious story, some of the common problems which companies are facing nowadays were presented. One of them is the lack of time. In this particular case, and in the majority of cases, people lack time because they are trapped doing repetitive tasks that don't add value, thus there is this constant feeling that it's impossible to achieve more ambitious goals. One of the main excuses that developers give when asked why they are not practicing TDD is the lack of time for writing tests.

This chapter tackles a possible solution for this, which is using Jenkins. A virtual machine with an instance of Jenkins was configured to automate some of the repetitive tasks that were draining time from the team.

Once the problems have been addressed, TDD becomes really handy. Every new feature developed in the TDD way will be more than covered by tests, then future changes on that feature will be run against the test suite, and this will fail if one of the tests is not satisfied...