Covering ClojureGiven, version 1.1.0.
ClojureGiven is a port of Jim Weirich's rspec-given BDD test framework to Clojure. ClojureGiven is implemented on top of clojure.test through a set of macros that provide a basic Given/When/Then notation.
Download from clojars.org - http://clojars.org/clojure-given
ClojureGiven is ready for production use.
Here is a specification written in the ClojureGiven framework:
(ns cljgiven.test.core (:use [cljgiven.core]) (:use [clojure.test])) (defspec basic-spec (Given [t1 (+ 1 x) t2 (- 2 t1)]) (Context "let us test t1" (Given [x (+ 1 3)]) (When result (+ 1 t1)) (Then (= 6 result))) (Context "let us test t2" (Given! [x (+ 1 3)]) (When result (+ t2 x)) (Then (= 2 result)))) ;this test is designed to fail (defspec stack (Given [stack init-obj]) (Context "testing a vector as a stack" (Given [init-obj [1 3]]) (When stack (conj stack 2)) ; push 2 on the stack (Then (= 2 (peek stack))) (Then (= [1 3 2] stack)) (Context "testing pop" (When stack (pop stack)) (Then (= [1 3] stack)))) (Context "testing a list as a stack" (Given [init-obj '(1 3)]) (When stack (conj stack 2)) ; push 2 on the stack (Then (= 2 (peek stack))) (Then (= '( 2 1 3) stack)) (Context "testing pop" (When stack (pop stack)) (Then (= '(1 3) stack)))))
Below is the output from "lein test"
Testing cljgiven.test.core FAIL in (basic-spec) (core.clj:15) basic-spec - let us test t2 expected: (= 2 result) actual: (not (= 2 1)) Ran 2 tests containing 8 assertions. 1 failures, 0 errors.
Let's talk about the individual statements used in the Given framework.
The Given section specifies a starting point, a set of preconditions that must be true before the code under test is allowed to be run. In standard test frameworks the preconditions are established with a combination of setup methods and code in the test.
In the example code above the preconditions are started with Given statements. A top level Given (that applies to the entire defspec block) says that two preconditions exist for a variable t1 & t2 with some dependent variable of "x".
Note that "x" are not specified in the top level defspec block, but are given in each of the nested contexts. By pushing the definition of "x" into the nested contexts, we can vary it as needed for that particular context.
A precondition in the form "(Given [var ])" creates a lazy accessor that is evaluated when the first reference is encountered. If any variable referenced in the expression the lazy accessor is will re-evaluate at the next reference. If you want a non-lazy given, use "(Given! [var ])".
The preconditions are run in order of definition. Nested contexts will inherit the preconditions from the enclosing context, with out preconditions running before inner preconditions.
The When block specifies the code to be tested or specified.
After the preconditions in the given section are met, the when code block is run.
There should only be one When block for a given context. However, a When in an outer context should be treated as a Given in an inner context. E.g.
(Context "outer context" (When code specified in the outer context ) (Then assert something about the outer context) (Context "inner context" ;At this point, the _When_ of the outer context ;should be treated as a _Given_ of the inner context (When code specified in the inner context) (Then assert something about the inner context)))
(When result (inc x))
The code block is executed once per test and the value of the code block is bound to 'result'.
The Then sections are the postconditions of the specification. These then conditions must be true after the code under test (the When block) is run.
The code in the Then block should be a single assertion. Code in Then blocks should not have any side effects.
(Then (= 1 result))
After the related When block is run, the value of result should be one. If it is not one, the test will fail.
Eclipse Public License 1.0, see http://opensource.org/licenses/eclipse-1.0.php.
Jim Weirich for creating rspec-given.