Specs

TestBox : Behavior Driven Development (BDD)
Search…
Specs
A spec is a declaration that will usually test your system with a requirement. They are defined by calling the TestBox it() global function, which takes in a title and a body function/closure. The title is the title of this spec you will write and the body function/closure is a block of code that represents the spec.
A spec will contain most likely one or more expectations that will test the state of the SUT (software under test) or sometimes referred to as code under test. In BDD style, your specifications are what is used to validate your requirements of a scenario which is your describe() block of your story.
1
function run(){
2
​
3
     describe("A suite", function(){
4
          it("contains spec with an awesome expectation", function(){
5
               expect( true ).toBeTrue();
6
          });
7
​
8
          it("contains a spec with more than 1 expectation", function(){
9
               expect( [1,2,3] ).toBeArray();
10
               expect( [1,2,3] ).toHaveLength( 3 );
11
          });
12
     });
13
​
14
}
Copied!
An expectation is a nice assertion DSL that TestBox exposes so you can pretty much read what should happen in the testing scenario. A spec will pass if all expectations pass. A spec with one or more expectations that fail will fail the entire spec.
The it() function is also aliased as then() - except it() has title when then() uses then instead
Arguments
Argument
Required
Default
Type
Description
title
true
---
string
the title of the spec
body
true
---
closure/udf
The closure that represents the spec
labels
false
---
string/array
The list or array of labels this suite group belongs to
skip
false
false
Boolean
A flag or a closure that tells TestBox to skip this suite group from testing if true. If this is a closure it must return boolean.
data
false
{}
struct
A struct of data you can bind the spec with so you can use within the body closure
They are closures Ma!
Since the implementations of the describe() and it() functions are closures, they can contain executable code that is necessary to implement the test. All CFML rules of scoping apply to closures, so please remember them. We recommend always using the variables scope for easy access and distinction.
1
function run(){
2
​
3
     describe("A suite is a closure", function(){
4
          c = new Calculator();
5
​
6
          it("and so is a spec", function(){
7
               expect( c ).toBeTypeOf( 'component' );
8
          });
9
     });
10
​
11
}
Copied!
Spec Data Binding
The data argument can be used to pass in a structure of data into the spec so it can be used later within the body closure. This is great when doing looping and creating dynamic closure calls:
1
// Simple Example
2
it( title="can handle binding", body=function( data ){
3
    expect(    data.keep ).toBeTrue();
4
}, data={ keep = true } );
5
​
6
// Complex Example. Let's iterate over a bunch of files and create dynamic specs
7
for( var filePath in files ){
8
​
9
  it( 
10
    title="#getFileFromPath( filePath )# should be valid JSON", 
11
    // pass in a struct of data to the spec for later evaluation
12
    data={ filePath = filePath },
13
    // the spec closure accepts the data for later evaluation
14
    body=function( data ) {
15
      var json = fileRead( data.filePath );
16
      var isItJson = isJSON( json );
17
​
18
      expect( json ).notToBeEmpty();
19
      expect( isItJson ).toBeTrue();
20
​
21
      if( isItJson ){
22
          var jsonData = deserializeJSON(json);
23
          if( getFileFromPath( filePath ) != "index.json"){
24
              expect( jsonData ).toHaveKey( "name" );
25
              expect( jsonData ).toHaveKey( "type" );
26
          }
27
      }
28
​
29
  });
30
}
Copied!
When using the then() function instead of it() the title argument name is then instead of title for the it() function
Dynamic Suites
Expectations
Last modified 2mo ago
Copy link
Edit on GitHub
Contents
Arguments
They are closures Ma!
Spec Data Binding