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

Possible improvements


In this section and the following subsections, we are going to tackle some of the problems described in Alice's story. Because the code we inherited from the example is already implemented, we can't apply TDD here. Instead, we are going to set the basis and prepare the ground for future developments where applying TDD will become very useful.

Although there are always many things that can be improved, the pain points being addressed are code merging issues, lots of manual testing, manual releases, and the length of time taken to develop changes or new features.

For the first two, we are going to increase the test coverage of the application and implement CI. A Jenkins server is going to be configured to address the third issue, manual releases. And finally, the last issue, which is the long time to market (TTM), is going to be mitigated by implementing the rest of the solutions.

Increasing test coverage

Among the metrics for measuring code quality, there is one that is...