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

History


During one of my several Agile incarnations, I had the opportunity to work with Tim Mackinnon who was involved in the development of the concept of mock objects. I don't want to infringe on his rights to tell the story himself, which he had told me during our little gig together. In a nutshell, it was thought up at a brainstorming session between some members of a London-based architecture group. They had discussed the antipattern of having to introduce getters into their classes to make them testable. This was in the very early stages of Agile (1999) and terms like "scrum" and "Extreme Programming" hadn't been coined yet.

Since then there has been a constant love-hate relationship between developers who like mock objects and can swear by their experiences of their usage and developers who think mocking is, well let's just say, not the best thing to use with Scala. A very...