test

Specs _ what it is : 

Specs _ what it is Scala library for Behaviour-Driven Development. import org.specs._ object HelloWorldSpec extends Specification { "'hello world' has 11 characters" in { "hello world".size must_== 11 } "'hello world' matches 'h.* w.*'" in { "hello world" must beMatching("h.* w.*") } } [info] Running specs tests... [info] [info] Testing scalamelb.specs.HelloWorldSpec ... [info] specifies [info] + 'hello world' has 11 characters [info] + 'hello world' matches 'h.* w.*' [info] [info] All tests PASSED. See the associated code for a working example - HelloWorldSpec.scala

Specs _ structure : 

Specs _ structure BDD builds on TDD to allow tests to be written in the business domain language. The Specs structure: Specify system (with context) and examples "An empty stack" should "be of size zero" "A Nigerian prince with access to an email account" should { "contact you in relation to his most generous offer" in { // exercise the logic and make assertions ... } } NigerianPrinceSpec.scala

Specs _ structure : 

Specs _ structure Examples can be nested Systems can't Specifications can, sort of "A snowflake" should { [info] A snowflake should "be cold" in { [info] + be cold "and icy" in { … } [info] + and icy "and unique" in { … } [info] + and unique "A snowflake" should { "in the desert" should { "melt" in { … } object SnowflakeSpec extends Specification { "A snowflake" isSpecifiedBy SnowflakeInTheDesertSpec, SnowflakeInTheFrideSpec, SnowflakeOnTheTongueSpec } SnowflakeSpec.scala

Specs _ matchers : 

Specs _ matchers Matchers are the assertion mechanism. Allow natural language assertions 100+ are documented at time of writing (v1.4.4) Can write custom matchers. Can be combinatorial. "A phone bill" should { "keep a count of calls made" in { bill.numberOfCallsMade must_== 3 PhoneBillSpec.scala "A phone bill" should { "include a call to my mother" in { bill.callsMade must contain("9898 4477") "A phone bill" should { "export calls to file" in { bill.exportFile must (beReadable and not(beHidden))

Specs _ scalacheck : 

Specs _ scalacheck Matcher for ScalaCheck (A test case automation tool) Default of 100 arbitrary test input values per statement For all n (where n >=0) vn² must equal n object SquareRooterSpec extends Specification with ScalaCheck { "A Square Rooter" should { "find the originally squared value (as long as it wasn't negative)" in { // forAll { (n: Int) => scala.Math.sqrt(n*n) == n } must pass // fails on -1 forAll { n: Int => n >= 0 ==> (scala.Math.sqrt(n*n) == n) } must pass SquareRooter.scala

Specs _ tear up / down : 

Specs _ tear up / down Traditional setup & teardown mechanisms available for before and after: Specification each System each Example object SetupAndTeardown extends Specification { doBeforeSpec{ println("Specification setup") } doFirst{ println("System setup") } doBefore{ println("Example setup") } … doAfter{ println("example teardown") } doLast{ println("System teardown") } doAfterSpec{ println("Specification teardown") } } SetupAndTeardown.scala

Specs _ shared contexts : 

Specs _ shared contexts Before and after context blocks can be encapsulated in Context values and "threaded" into Systems. They come with a warning – expect the unexpected if shared and mutated in different Systems within the Specification. And don't feed after midnight. var listOfStrings:List[String] = Nil val withThreeValues = beforeContext { listOfStrings = "bob" :: "harry" :: "dorothy" :: Nil } "A list of three Strings" ->-(withThreeValues) should { "be of three strings long" in { listOfStrings.length must_== 3 } } ThreadedLists.scala

Specs _ system contexts : 

Specs _ system contexts Alternatively, System Contexts can be constructed to always return a system in a given state. They come in two flavours: Internal (a SystemContext instance) External (a case class extending SystemContext) object MonkeyKingSpec extends Specification with SystemContexts { /* Demonstrates explicit, internal system context. See example for more. */ "The monkey king under attack" should { val monkeyKingUnderAttack = systemContext { new MonkeyKing(true) } "summon warriors from his ear hairs".withA(monkeyKingUnderAttack) { monkeyKing => monkeyKing.summonsWarriorsFromEarHair must beTrue MonkeyKing.scala

Specs _ mocking : 

Specs _ mocking Both jMock and Mockito can be mixed-in Specs adds syntactic sugar to ease mocking object USBLightSpec extends Specification with Mockito { "A green USB light" should { "be observed but not adjusted" in { val light = mock[Light] light.getColour returns Green val colour = LightObserver(light).observeLightsColour colour must_== Green light.getColour was called light.setIntensity _ wasnt called USBLightSpec.scala

Specs _ alternatives : 

Specs _ alternatives ScalaTest Instinct class StackSpec extends Spec with ShouldMatchers { describe("A newly created Stack") { val stack = new Stack[Any] it("should be empty") { stack should be ('empty) } } } class ANewlyCreatedStack { val stack = new Stack[Any] @Specification def shouldBeEmpty = { expect that stack.depth isEqualTo 0 } }