I've got some fixtures that boot up and close the database in my project.
Now it looks something like this:
(use-fixtures :once with-embedded-db)
while in the fixture itself I've got a dynamic variable that I use in different places:
(def ^:dynamic *db*)
(defn with-embedded-db [f]
(binding [*db* (db/connect args)]
(f)
(finally
(db/clean-up *db)))
Now, assume that db/connect and db/clean-up take some time.
PROBLEM:
When I run tests using lein test, it takes very long time, unnecessarily spending time on connecting and disconnecting to the db for every namespace.
QUESTION:
Is there a way to set up global fixtures so that when I run lein test, it calls it only once for all the test namespaces?
Thanks!
It would have been better if that feature was added to leiningen itself. At least a ticket should be opened, if not a PR.
The following solution is dirty, but you can get the idea and transform it into something more intelligent.
;; profect.clj
:profiles
{:dev {:dependencies [[robert/hooke "1.1.2"]]
:injections [(require '[robert.hooke :as hooke])
(defn run-all-test-hook [f & nss]
(doall (map (fn [a]
(when (intern a '*db*)
(intern a '*db* "1234"))) nss))
(apply f nss))
(hooke/add-hook #'clojure.test/run-tests #'run-all-test-hook)
]}}
Note: leiningen itself uses robert/hooke in its core.
And then somewhere in tests:
(ns reagenttest.cli
(:require [clojure.test :refer :all]))
(def ^:dynamic *db*) ;; should be defined in every NS where it is needed
(deftest Again
(testing "new"
(prn *db*)))
Use circleci.test, it supports :global-fixtures:
... you can define global fixtures that are only run once for the entire test run, no matter how many namespaces you run.
Related
Question
I would like to black hole print like behaviors within my test bodies in order to keep my log output looking clean and tidy.
(deftest some-test
(testing "something"
(logless
(is (= 22 (test-thing 14))))))
I expect test-thing to call println and other similar calls to *out* and would like those to stop polluting my test output.
Is there a recognized way to do this in general?
I found this guy (with-out-str) but it's capturing the string, not quite what I'm looking for.
Background
I'm fairly new to Clojure, coming largely from a javascript world. Having a blast so far! But there's lots left for me to learn.
In Clojure, not Clojure.script (if it matters)
Just use with-out-str and then ignore the string.
Note that this will not capture error messages or messages from Java libraries. If you want to capture and/or suppress this output, I have written 3 additional functions in the Tupelo library that you may find useful:
with-err-str
with-system-err-str
with-system-out-str
The code looks like this:
(defmacro with-system-err-str
"Evaluates exprs in a context in which JVM System/err is bound to a fresh
PrintStream. Returns the string created by any nested printing calls."
[& body]
`(let [baos# (ByteArrayOutputStream.)
ps# (PrintStream. baos#)]
(System/setErr ps#)
~#body
(System/setErr System/err)
(.close ps#)
(.toString baos#)))
If you wanted, you could make a new macro like so:
(defmacro with-printing-suppressed
"Evaluates exprs in a context in which JVM System/err and System/out captured & discarded."
[& body]
`(let [baos# (ByteArrayOutputStream.)
ps# (PrintStream. baos#)
s# (new java.io.StringWriter)]
(System/setErr ps#)
(System/setOut ps#)
(binding [*err* s#
*out* s#]
(let [result# (do ~#body)]
(.close ps#)
(System/setErr System/err)
(System/setOut System/out)
result#))))
(defn stuff []
(println "***** doing stuff *****")
42)
and then test it:
(println "calling - before")
(is= 42 (with-printing-suppressed
(stuff)))
(println "calling - after")
with result:
calling - before
calling - after
Use default logging and logback.xml for output configuration.
default clojure logging
I'm running into some issues with reporting on failures using the clojure.test testing framework.
Now, I understand that I can override some functions for different reporting so that it prints out to the console or wherever I want it to print to. I also understand that I can save this output to a file.
My issue is the following... when I declare a deftest like this example:
(deftest test1
(is (= 1 1)
(is (= 2 1))
This test will run and if I do something like (run-tests) or (test-var #'test1) it will return nil but print the failures.
I decided to override the :fail method for reporting, because what I want is a map of the failures like this: {"expected" (:expected m), "actual" (:actual m)} and this kinda sorta works if I were to just use the reporting function.
The problem is that when you run tests through the Clojure.test framework there are many macro's that get called and it doesn't behave it exactly how I want to.
My end goal is: running the tests, and if there are any failures, instead of printing them, save them to a map and return the map to me. If they all pass, then I don't care what it returns to me.
Is this even possible? I don't want to stop testing if a certain test fails, I just want it to be logged somewhere, preferably a map.
Sources:
Clojure test with mutiple assertions
https://clojure.github.io/clojure/branch-1.1.x/clojure.test-api.html
https://groups.google.com/forum/#!topic/clojure/vCjso96wqps
I'm afraid there's no easy way how to do that.
You could provide a custom implementation of clojure.test/report :fail defmethod and store the result in an atom but it's hard to propage the result to outer layers.
If you just use test-var then it's doable but note that test fixtures aren't executed in this case - see test-vars source:
(:use clojure.test)
(deftest failing
(testing "fail me"
(is (= 1 0))
(is (= 2 1))
(is (= 3 2))))
(def test-failures (atom []))
(defmethod report :fail [m]
(swap! test-failures
(fn [previous-failures current-failure]
(conj previous-failures current-failure))
{:test-var-str (testing-vars-str m)
:expected (:expected m)
:actual (:actual m)}))
(defmethod report :end-test-var [m]
#test-failures)
(defn run-test-var [v]
(reset! test-failures [])
(test-var v))
;; in REPL:
(run-test-var #'failing)
;; =>
[{:test-var-str "(failing) (form-init4939336553149581727.clj:159)", :expected 1, :actual (0)}
{:test-var-str "(failing) (form-init4939336553149581727.clj:160)", :expected 2, :actual (1)}
{:test-var-str "(failing) (form-init4939336553149581727.clj:161)", :expected 3, :actual (2)}]
There's also defmethod report :end-test-ns but this one is not very useful because test-ns function returns #*report-counters*.
I'm trying to use CLX while learning common lisp, because I figure it's more effective to learn if I have an actual, tangible, practical result. Unfortunately, I can't get CLX to work. I followed the first bit of this tutorial, after installing the clisp and clisp-module-clx packages in debian.
I think I'm just horribly misunderstanding clisp's package / module / etc. loading system, but I can't find any resources for how to do this.
foo.lisp:
(defun pop-up-window (life-time &optional (host ""))
(let* ((display (xlib:open-display host))
(screen (first (xlib:display-roots display)))
(root-window (xlib:screen-root screen))
(my-window (xlib:create-window
:parent root-window
:x 0
:y 0
:width 200
:height 300)))
(xlib:map-window my-window)
(xlib:display-finish-output display)
(format t "it should be here ~%")
(sleep life-time)
(xlib:destroy-window my-window)
(xlib:close-display display)
)
(pop-up-window 10)
output: there is no package with name "XLIB"
Edit:
I tried (require "clx") at the start of my code, but I get #<PACKAGE COMMON-LISP> is locked.
The CLX system was most likely not installed. You could download the archive yourself and configure ASDF to load the system, but the easiest route is to first install Quicklisp. Then, you can execute:
(ql:quickload :clx)
This downloads, compiles and loads the desired system and all its dependencies. This step should be executed each time you restart your Lisp environment. As soon as you need more than one libraries, you should also define your own system (for example in ~/quicklisp/local-projects/) and load that one instead.
I'm having some issues with testing a clojure macro. When I put the code through the repl, it behaves as expected, but when I try to expect this behavior in a test, I'm getting back nil instead. I have a feeling it has to do with how the test runner handles macroexpansion, but I'm not sure what exactly is going on. Any advice/alternative ways to test this code is appreciated.
Here is a simplified example of the macro I'm trying to test
(defmacro macro-with-some-validation
[-name- & forms]
(assert-symbols [-name-])
`(defn ~-name- [] (println "You passed the validation")))
(macroexpand-1 (read-string "(macro-with-some-validation my-name (forms))"))
;; ->
(clojure.core/defn my-name [] (clojure.core/println "You passed the validation"))
When passed into the repl
(macroexpand-1 (read-string "(macro-with-some-validation 'not-symbol (forms))"))
;; ->
rulesets.core-test=> Exception Non-symbol passed in to function. chibi-1-0-0.core/assert-symbols (core.clj:140)
But when put through a test
(deftest macro-with-some-validation-bad
(testing "Passing in a non-symbol to the macro"
(is (thrown? Exception
(macroexpand-1 (read-string "(macro-with-some-validation 'not-symbol (forms))"))))))
;; after a lein test ->
FAIL in (macro-with-some-validation-bad) (core_test.clj:50)
Passing in a non-symbol to the macro
expected: (thrown? Exception (macroexpand-1 (read-string "(macro-with-some-validation 'not-symbol (forms))")))
actual: nil
Thanks.
Edit: forgot to include the source for assert-symbols in case it matters
(defn assert-symbol [symbol]
(if (not (instance? clojure.lang.Symbol symbol))
(throw (Exception. "Non-symbol passed in to function."))))
(defn assert-symbols [symbols]
(if (not (every? #(instance? clojure.lang.Symbol %) symbols))
(throw (Exception. "Non-symbol passed in to function."))))
After changing my read-strings to be ` instead, I'm able to get the code working again. Still strange that read-string wasn't working correctly, though. Thanks for the help.
When using clojure.test's use-fixture, is there a way to pass a value from the fixture function to the test function?
A couple of good choices are dynamic binding and with-redefs. You could bind a var from the test namespace in the fixture and then use it in a test definition:
core.clj:
(ns hello.core
(:gen-class))
(defn foo [x]
(inc x))
test/hello/core.clj:
(ns hello.core-test
(:require [clojure.test :refer :all]
[hello.core :refer :all]))
(def ^:dynamic *a* 4)
(defn setup [f]
(binding [*a* 42]
(with-redefs [hello.core/foo (constantly 42)]
(f))))
(use-fixtures :once setup)
(deftest a-test
(testing "testing the number 42"
(is (= *a* (foo 75)))))
You can tell that it works by comparing calling the test directly, which does not use fixtures, to calling it through run-tests:
hello.core-test> (a-test)
FAIL in (a-test) (core_test.clj:17)
testing the number 42
expected: (= *a* (foo 75))
actual: (not (= 4 76))
nil
hello.core-test> (run-tests)
Testing hello.core-test
Ran 1 tests containing 1 assertions.
0 failures, 0 errors.
{:test 1, :pass 1, :fail 0, :error 0, :type :summary}
This approach works because fixtures close over the tests they run, though they don't get to actually make the calls to the test functions directly (usually) so it makes sense to use closures to pass information to the test code.
Perhaps not a direct answer, but if your fixture was an :each fixture anyway, or you can tolerate it being an :each fixture, you can just cop out and create a set-up function returning the relevant state and call it as the first line of your test, instead of using a fixture. This may be the best approach for some circumstances.
(defn set-up [] (get-complex-state))
(deftest blah
(let [state (set-up)]
(frobnicate)
(query state)
(tear-down state)))