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

Coupling


In software parlance, coupling refers to the gradation of interdependence between different modules. It measures how much impact does a change in one routine have in another. We can broadly distinguish between two major types of coupling: tight coupling and loose coupling. Two modules are considered tightly coupled if you cannot change one module without having a cascading effect on the second module. On the contrary, if one module can change resulting in little or no change in the other module, they are considered loosely coupled.

Coupling plays a major role in testability of your code. The more loosely coupled your code is, the more testable it is. It is not always easy to reduce or eliminate coupling, but since the introduction of dependency injection, it has become easier to test a module in isolation.

Note

Dependency injection, also known as Inversion of Control (IoC), is a design pattern in which a dependency object (for example, a service) is passed in as a dependency to the...