This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-18
Channels
- # announcements (6)
- # babashka (16)
- # beginners (194)
- # calva (20)
- # cider (34)
- # clj-kondo (38)
- # clojure (89)
- # clojure-europe (10)
- # clojure-finland (15)
- # clojure-italy (2)
- # clojure-nl (15)
- # clojure-sg (7)
- # clojure-spec (15)
- # clojure-uk (86)
- # clojurebridge (1)
- # clojurescript (60)
- # community-development (11)
- # conjure (13)
- # core-async (48)
- # core-typed (3)
- # cursive (22)
- # datascript (8)
- # datomic (40)
- # duct (11)
- # emacs (3)
- # figwheel-main (22)
- # fulcro (45)
- # graphql (1)
- # helix (9)
- # hoplon (15)
- # hugsql (7)
- # jobs-discuss (47)
- # juxt (7)
- # kaocha (21)
- # luminus (1)
- # malli (13)
- # meander (2)
- # off-topic (52)
- # parinfer (19)
- # re-frame (66)
- # reagent (1)
- # reitit (3)
- # ring-swagger (1)
- # rum (2)
- # shadow-cljs (72)
- # spacemacs (5)
- # sql (4)
- # timbre (5)
- # tools-deps (15)
- # vim (5)
- # vrac (7)
Hi everyone! I tried to run a kaocha test in a nextjournal clojure notebook, but with no success. Does anybody have an example notebook that contains a running kaoacha test?
I do not even know, how the test.edn should look like. What would the test path look like for a nextjournal notebook?
those are not on the file system, they are sent to the runner directly, so Kaocha will not be able to find those.
it's actually an interesting case... never thought it about it much before. You would want to build up a test plan solely based on defined vars, without scanning the file system.
do you need kaocha? seems like a use case where a simple clojure.test/run-all-tests
might suffice?
I think clojure
is installed in nextjournal right? Can't one just run clojure -Sdeps '{:deps {kaocha ...}}' -m ...
?
yes, that's not the problem. The problem is that kaocha doesn't "see" any of the code that's defined in code cells.
@lomin are you familiar with the mount functionality? if you go into runtime settings you can "mount" a code listing at a certain path on the filesystem
ok, this seems to be more cumbersome than I thought. I was hoping that I was doing something wrong 😉 I try to come with a workaround. Thanks for your help.