Book Image

Scala Test-Driven Development

By : Gaurav Sood
Book Image

Scala Test-Driven Development

By: Gaurav Sood

Overview of this book

Test-driven development (TDD) produces high-quality applications in less time than is possible with traditional methods. Due to the systematic nature of TDD, the application is tested in individual units as well as cumulatively, right from the design stage, to ensure optimum performance and reduced debugging costs. This step-by-step guide shows you how to use the principles of TDD and built-in Scala testing modules to write clean and fully tested Scala code and give your workflow the change it needs to let you create better applications than ever before. After an introduction to TDD, you will learn the basics of ScalaTest, one of the most flexible and most popular testing tools around for Scala, by building your first fully test-driven application. Building on from that you will learn about the ScalaTest API and how to refactor code to produce high-quality applications. We’ll teach you the concepts of BDD (Behavior-driven development) and you’ll see how to add functional tests to the existing suite of tests. You’ll be introduced to the concepts of Mocks and Stubs and will learn to increase test coverage using properties. With a concluding chapter on miscellaneous tools, this book will enable you to write better quality code that is easily maintainable and watch your apps change for the better.
Table of Contents (16 chapters)
Scala Test-Driven Development
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface

Red-Green-Refactor


I first heard the term "refactor mercilessly" from the person responsible for hand-holding and inducting me into the Agile process. It was originally coined as part of eXtreme Programming (XP), which is one of the several popular Agile processes that involve very short iterations, continuous releases, and paired-programming. After spending more than a decade with these processes, I can undoubtedly say that there is no way to refactor other than mercilessly. You can't do it half-heartedly or incompletely, as it accumulates as tech debt, but at some stage there is no other way but to do a big bang refactoring exercise. If you have been using Agile previously then you would know how easy it is to ignore refactoring and then end up going through a massive refactoring story to clear up the technical debt.

It is always recommended that you take into account the refactoring effort as part of the story estimation process.

Refactoring is the last straw in our test-driven cycle (Red...