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

Code smell


Code smell in the source code is any indication on the surface of the programming code that hints at a deeper problem. This can be as trivial as an oversized method. The most accurate indication of a code smell is the testability of the code. If the code can be tested in a very simple and straightforward test then that means the code is not tightly coupled. This also means that the code is doing only one task, which can be tested end to end.

 

"a code smell is a surface indication that usually corresponds to a deeper problem in the system"

 
 --Martin Fowler

There are a few types of code smell that can be identified by looking at the code.

Expendable

An expendable is something gratuitous and futile. Removal of such code will make the code cleaner, efficient, and comprehensible. It can be one of the following:

  • Comments: As programmers, we sometimes tend to do things in the most cryptic way possible and then write lines of comments around the code to explain what ingenious solution we...