This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-27
Channels
- # aws (7)
- # babashka (145)
- # beginners (83)
- # calva (18)
- # cider (11)
- # clara (9)
- # clj-kondo (59)
- # cljdoc (4)
- # cljs-dev (4)
- # cljsrn (11)
- # clojure (168)
- # clojure-australia (21)
- # clojure-dev (5)
- # clojure-europe (46)
- # clojure-italy (3)
- # clojure-nl (10)
- # clojure-taiwan (1)
- # clojure-uk (55)
- # clojurescript (85)
- # clojureverse-ops (1)
- # code-reviews (3)
- # conjure (22)
- # cursive (3)
- # datahike (3)
- # datomic (4)
- # emacs (5)
- # helix (20)
- # jackdaw (1)
- # jobs (2)
- # jobs-discuss (7)
- # lsp (1)
- # malli (5)
- # off-topic (85)
- # other-languages (4)
- # practicalli (4)
- # reitit (2)
- # releases (2)
- # sci (62)
- # shadow-cljs (181)
- # testing (5)
- # tools-deps (15)
- # xtdb (31)
If they are deftests I can run them with shortcuts in my editor and I can use setup code / fixtures.
👍 3
it doesn't seem to invoke the fixtures for the nested tests. So the behavior will be different depending on if you call the tests individually vs the grouped thing. I think that makes it less useful
oo, that’s tough
another idea: have the top-level tests marked with ^:subtest
, but put the implementation in a function that you can call from c-test
too?
(defn a-test-fn []
(is (= 1 2)))
(defn b-test-fn []
(is (= 1 2)))
(deftest ^:subtest a-test
(a-test-fn))
(deftest ^:subtest b-test
(b-test-fn))
(deftest c-test
(a-test-fn)
(b-test-fn))