This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-22
Channels
- # announcements (1)
- # babashka (28)
- # beginners (120)
- # braveandtrue (6)
- # calva (59)
- # cider (10)
- # clj-kondo (10)
- # cljfx (2)
- # clojure (66)
- # clojure-europe (20)
- # clojure-germany (1)
- # clojure-italy (3)
- # clojure-nl (4)
- # clojure-norway (1)
- # clojure-serbia (17)
- # clojure-spain (1)
- # clojure-uk (17)
- # clojurescript (120)
- # clojureverse-ops (4)
- # core-async (5)
- # cursive (18)
- # data-oriented-programming (1)
- # datomic (4)
- # deps-new (8)
- # emacs (14)
- # fulcro (16)
- # funcool (2)
- # kaocha (4)
- # lambdaisland (5)
- # luminus (1)
- # malli (47)
- # membrane (9)
- # mid-cities-meetup (2)
- # music (1)
- # off-topic (44)
- # pathom (13)
- # practicalli (2)
- # re-frame (15)
- # reagent (34)
- # reveal (25)
- # ring (56)
- # rum (1)
- # shadow-cljs (23)
- # sql (14)
- # startup-in-a-month (1)
- # tools-deps (10)
- # vim (9)
- # vscode (3)
- # xtdb (9)
is there some built-in way to make kaocha.runner
return a non-zero exit code if there were 0 tests ran?
we have encountered it twice within 2 weeks in 2 different projects that the CI was misconfigured and reported false positive test results, because 0 tests ran.
@onetom, I would prefer a non zero exit in this scenario as well. But... it is also pretty easy to write https://github.com/lread/test-doc-blocks/blob/65bddd419c29f0e3ef8146aa11111df12bd7c1fd/tests.edn#L12 to achieve this.
👍 3
thanks! I just heard, my colleague actually created a GitHub issue about this: https://github.com/lambdaisland/kaocha/issues/211 I will add your suggestion there.