This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-18
Channels
- # announcements (1)
- # babashka (15)
- # beginners (152)
- # calva (28)
- # circleci (1)
- # clj-kondo (24)
- # cljsrn (8)
- # clojure (137)
- # clojure-berlin (3)
- # clojure-czech (2)
- # clojure-dev (20)
- # clojure-europe (69)
- # clojure-finland (5)
- # clojure-france (3)
- # clojure-italy (11)
- # clojure-my (1)
- # clojure-nl (4)
- # clojure-uk (15)
- # clojuredesign-podcast (1)
- # clojurescript (13)
- # conjure (15)
- # cursive (13)
- # datomic (41)
- # deps-new (50)
- # events (1)
- # fulcro (9)
- # graalvm (27)
- # joker (2)
- # kaocha (11)
- # off-topic (22)
- # pathom (48)
- # rdf (6)
- # reagent (25)
- # reitit (47)
- # reveal (10)
- # ring-swagger (1)
- # rum (4)
- # sci (27)
- # shadow-cljs (73)
- # tools-deps (49)
- # vrac (2)
- # xtdb (4)
putting out a new release with some smaller improvements, the main one is that Ctrl-C should be much more reliable now. If you are midway through a test run and you see there are some failing tests, you can interrupt it to see the details of the failures. This was always supposed to work but half of the time it didn't.
this also contains an improvement where we skip over group tests (e.g corresponding with a namespace) if there is nothing inside the group to test. This is mainly done because the spec-test-check plugin generates a test for each ns, even if it doesn't have any fdef's in it. So instead of [()()()()()(..)]
you now will just see [(..)]
also if you are using the spec-test-check plugin you can run only your generated tests with bin/kaocha generative-fdef-checks
, since it's really just a test suite. This should have worked before but because of the order things happen the test suite got added after the filtering had already happened, so it would always run, even when doing e.g. bin/kaocha unit
.
Would I be right in thinking that the kaocha.hooks/pre-run
will be run only once before all the tests are run and similiarly, the kaocha.hooks/post-run
after all the tests are run?
similarly pre-load
/ post-load
run once, pre-load-test
/ post-load-test
run once for each tests (unfortunately we're stuck with the inconsistent naming)