Running cljs.test tests on node.js using doo and karma

Francesc and I are using doo and Karma to run our cljs.test tests on Node.js.

This is what we did to make it work.

First we installed Node.js, and then, Karma and its CLI following these instructions.

Once we had that, we added the doo plugin to the project.clj.

	...
	...
	:plugins [[lein-cljsbuild "1.1.1"]
	[lein-doo "0.1.6"]]
	...
	...

view raw plugins_in_project.clj hosted with ❤ by GitHub

doo is a library and leiningen plugin that allows to run cljs.test on different JavaScript environments.

Next, we created a new namespace for the unit tests in the tests directory, and set up the test build in project.clj (we called the new namespace unit-tests):

	...
	...
	:cljsbuild {:builds [...
	{:id "unit-tests"
	:source-paths ["src/cljs" "test"]
	:compiler {:output-to "out/unit_tests.js"
	:main 'math-ops.unit-tests
	:optimizations :none}}]}
	...
	...

view raw unit_tests_build_setup_in_project.clj hosted with ❤ by GitHub

Notice that in the setup you’ve to define which namespace will be used as the main of the unit tests: :main 'math-ops.unit-tests

In that namespace, we used doo to run the tests and register the namespaces containing unit tests:

	(ns math-ops.unit-tests
	(:require
	[doo.runner :refer-macros [doo-tests]]
	[math-ops.operations-test]
	[math-ops.operations-guessing-test]))
	(doo-tests
	'math-ops.operations-test
	'math-ops.operations-guessing-test)

view raw unit_tests.cljs hosted with ❤ by GitHub

Every time a new namespace containing unit tests is added, it has to be registered using the doo-tests macro in order to include it in the run.

Finally, to run the tests on Node.js we added it as a target to the build setup in project.clj:

	...
	...
	:cljsbuild {:builds [...
	...
	{:id "unit-tests"
	:source-paths ["src/cljs" "test"]
	:compiler {:output-to "out/unit_tests.js"
	:main 'math-ops.unit-tests
	:target :nodejs
	:optimizations :none}}]}
	...
	...

view raw build_setup_targetting_node_in_project.clj hosted with ❤ by GitHub

Notice the addition of :target :nodejs to the compiler options.

Then we could run our tests writing lein doo node unit-tests on the console:

	trikitrok@trikitrok:/home/trikitrok/Clojure/0_MiClojure/math-ops$ lein doo node unit-tests
	Building ...
	Analyzing jar:file:/home/trikitrok/.m2/repository/org/clojure/clojurescript/1.7.170/clojurescript-1.7.170.jar!/cljs/core.cljs
	... done. Elapsed 2.950936503 seconds
	;; ======================================================================
	;; Testing with Node:
	Testing math-ops.operations-test
	Testing math-ops.operations-guessing-test
	Ran 2 tests containing 18 assertions.
	0 failures, 0 errors.
	Watching paths: /home/trikitrok/Clojure/0_MiClojure/math-ops/src/cljs, /home/trikitrok/Clojure/0_MiClojure/math-ops/test

view raw console_tests.sh hosted with ❤ by GitHub

By default, doo watches the files in the source paths that we indicated in the build setup: :source-paths ["src/cljs" "test"], so any change to a file in them, makes the unit test run again.

You can check the code in this repository.

References:

• doo
• Karma
• How can you test ClojureScript applications and libraries?
• cljs.test