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

Integration testing


Individual components of the software module are tested together during integration testing. This phase sits in between unit testing and acceptance testing. In unit testing, we are testing a single unit of the code, whether it be a class or a method. Once we are sure that the individual bits are working according to the specification, we can start with integration testing to check if the modules/components behave as expected with other components, both internal and external.

The process of integration testing can be broken down into these steps:

  1. Identify the interfaces between the units that are used for interaction.

  2. Specify a collection of units with interfaces that form a complete end-to-end integration.

  3. Create integration test cases along with the inputs and expected outputs.

  4. Evaluate the test to determine if the results are matched and record the results.

Functional testing

We can think of functional testing as a verification activity. It is a type of black-box testing....