It's a TDD/BDD framework for Clojure and Clojurescript, based on RSpec.

Installation | Clojure | ClojureScript

lein new speclj YOUR_PROJECT_NAME

See @trptcolin's speclj template

Include speclj in your :dev profile :dependencies and:plugins. Then change the :test-path to "spec"

; - snip
:dependencies [[org.clojure/clojure "1.5.1"]]
:profiles {:dev {:dependencies [[speclj "3.0.0"]]}}
:plugins [[speclj "3.0.0"]]
:test-paths ["spec"]

1. Check out the source code: https://github.com/slagyr/speclj
2. Install it:

$ lein install

#Clojure

All your speclj code should go into a a directory named spec at the root of your project. Conventionally, the spec directory will mirror the src directory structure except that all the spec files will have the '_spec.clj' postfix.

| sample_project
|-- project.clj
|-- src
    |-- sample
        |-- core.clj
        | (All your other source code)
|-- spec
    |-- sample
        |-- core_spec.clj
       	| (All your other test code)

Checkout this example spec file. It would be located at sample_project/spec/sample/core_spec.clj. Below we'll look at it piece by piece.

(ns sample.core-spec
  (:require [speclj.core :refer :all]
            [sample.core :refer :all]))

(describe "Truth"

  (it "is true"
    (should true))

  (it "is not false"
    (should-not false)))

(run-specs)

Your spec files should :require the speclj.core in it's entirety. It's a clean namespace and you're likely going to use all the definitions within it. Don't forget to pull in the library that you're testing as well (sample.core in this case).

(use 'speclj.core)
(use 'sample.core)

describe is the outer most container for specs. It takes a String name and any number of spec components.

(describe "Truth" ...)

it specifies a characteristic of the subject. This is where assertions go. Be sure to provide good names as the first parameter of it calls.

(it "is true" ...)

Assertions. All assertions begin with should. should and should-not are just two of the many assertions available. They both take expressions that they will check for truthy-ness and falsy-ness respectively.

(should ...)
(should-not ...)

At the very end of the file is an invocation of (run-specs). This will invoke the specs and print a summary. When running a suite of specs, this call is benign.

(run-specs)

There are several ways to make assertions. They are documented on the wiki: Should Variants

it or characteristics are just one of several spec components allowed in a describe. Others like before, with, around, etc are helpful in keeping your specs clean and dry. Check out the listing on the wiki: Spec Components

Speclj includes a Leiningen task to execute speclj.main.

$ lein spec

The command below will run all the specs found in "spec" directory.

$ lein run -m speclj.main

The command below will run all the specs found in "spec" directory.

$ java -cp <...> speclj.main

The command below will start a process that will watch the source files and run specs for any updated files.

$ lein spec -a

There are several options for the runners. Use the --help options to see them all. Or visit Command Line Options.

$ lein spec --help

To make your tests start up slightly faster, you can add :speclj-eval-in :leiningen to your project map.

#ClojureScript

All your speclj code should go into a a directory named spec at the root of your project. Conventionally, the spec directory will mirror the src directory structure except that all the spec files will have the '_spec.clj' postfix.

| sample_project
|-- project.clj
|-- bin
    |-- speclj.js
|-- src
    |-- cljs
    	|-- sample
        	|-- core.cljs
        	| (All your other source code)
|-- spec
    |-- cljs
    	|-- sample
        	|-- core_spec.cljs
       		| (All your other test code)

lein-cljsbuild is a Leiningen plugin that'll get you up and running with ClojureScript. You'll need to add a :cljsbuild configuration map to your project.clj.

:cljsbuild {:builds        {:dev  {:source-paths ["src/cljs" "spec/cljs"]
                                   :compiler     {:output-to "path/to/compiled.js"}
                                   :notify-command ["bin/speclj" "path/to/compiled.js"]}
                            :prod {:source-paths  ["src/cljs"]
                                   :compiler      {:output-to "path/to/prod.js"
                                                   :optimizations :simple}}}
            :test-commands {"test" ["bin/speclj" "path/to/compiled.js"]}}

Speclj works by operating on your compiled ClojureScript. The :notify-command will execute the bin/speclj command after your cljs is compiled. The bin/speclj command will use speclj to evaluate your compiled ClojureScript.

Create a file named speclj in your bin directory and copy the code below:

#! /usr/bin/env phantomjs

var fs = require("fs");
var p = require('webpage').create();
var sys = require('system');

p.onConsoleMessage = function (x) {
    fs.write("/dev/stdout", x, "w");
};

p.injectJs(phantom.args[0]);

var result = p.evaluate(function () {
  speclj.run.standard.armed = true;
  return speclj.run.standard.run_specs(
     cljs.core.keyword("color"), true
  );
});

phantom.exit(result);

Checkout this example spec file. It would be located at sample_project/spec/cljs/sample/core_spec.cljs. Below we'll look at it piece by piece.

(ns sample.core-spec
  (:require-macros [speclj.core :refer [describe it should should-not run-specs])
  (:require [speclj.core]
            [sample.core :as my-core]))

(describe "Truth"

  (it "is true"
    (should true))

  (it "is not false"
    (should-not false)))

(run-specs)

Your spec files should :require the speclj.core just like in clojure. Don't forget to pull in the library that you're testing as well (sample.core in this case).

You'll also need to :require-macros the speclj.core and :refer each speclj test word that you want to use. In the example below, we are using describe, it, should, should-not, and run-spec. If you wanted to use context you would simply add it to the current :refer collection. For a list of speclj test words go to the speclj documentation

As a final note, your own library must be aliased using :as. This is a current ClojureScript requirement.

(:require-macros [speclj.core :refer [describe it should should-not run-specs])
(:require [speclj.core]
          [sample.core :as my-core]))

We defer to cljsbuild to run our test command.

$ lein cljsbuild test

The command below will start a process that will watch the source files and run specs for any updated files.

$ bin/speclj path/to/compiled.js

• Source code: https://github.com/slagyr/speclj
• Wiki: https://github.com/slagyr/speclj/wiki
• Email List: http://groups.google.com/group/speclj

speclj uses Leiningen version 2.0.0 or later.

Clone the master branch, build, and run all the tests:

$ git clone https://github.com/slagyr/speclj.git
$ cd speclj
$ lein spec

To make sure tests pass ClojureScript too:

lein cljsbuild clean
lein cljsbuild once

Make patches and submit them along with an issue (see below).

Post issues on the speclj github project:

• https://github.com/slagyr/speclj/issues

• Speclj 2.* requires Clojure 1.4.0+
• Clojure 1.3 is not supported by any version of Speclj due to a bug in Clojure 1.3.

Copyright (C) 2010-2014 Micah Martin All Rights Reserved.

Distributed under the The MIT License.