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

Acceptance specification


Acceptance specification is distinguished from unit specification by separating the test code from the expectation definition. Let's look at another example of how to use acceptance specification in Specs2:

package com.packt 
 
import org.specs2.Specification 
 
class ExampleAcceptanceSpec extends Specification { def is = 
  "Our example specification"      ^ 
      "and we should run t1 here"          ! t1 ^ 
      "and we should run t2 here"  ! t2 
 
    def t1 = success 
    def t2 = pending 
} 

The thing not to be missed here is the specification that is imported. Unlike the unit specification, we are importing org.spec2.Specification here instead of org.spec2.mutable.Specification.

In this example, the is method is the one that bootstraps the entire test. A fragment, which contains all the examples, is returned in this method.

The technique gives back a Fragments object containing every one of the cases...