This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-02-06
Channels
- # aleph (43)
- # announcements (11)
- # babashka (35)
- # beginners (70)
- # calva (4)
- # cider (8)
- # clerk (15)
- # clojure (192)
- # clojure-dev (7)
- # clojure-europe (44)
- # clojure-nl (2)
- # clojure-norway (65)
- # clojure-uk (4)
- # code-reviews (4)
- # conjure (1)
- # cursive (41)
- # data-science (1)
- # datomic (8)
- # emacs (7)
- # fulcro (13)
- # humbleui (17)
- # hyperfiddle (53)
- # kaocha (4)
- # malli (7)
- # missionary (17)
- # music (1)
- # obb (1)
- # off-topic (8)
- # polylith (1)
- # portal (3)
- # releases (11)
- # shadow-cljs (36)
- # squint (4)
- # tools-deps (4)
is there an example somewhere showing how to integrate kaocha-cljs2 into a codebase that already has a bunch of clj/jvm tests?
specifically, how to deal with the addition to tests.edn :tests [{:type :kaocha.type/cljs2}]
which bricks the ability for kaocha to find clj/jvm tests
also, although the tests show in the web interface (and it's really cool), the tests can't be found by the command line runner. i see traffic on tunnel when running the cmd line runner, though, and, if i run it while the web tab isn't open yet, it hangs until i do.
On finding jvm tests, if you set up your tests.edn like that you only have a cljs test suite, add a second suite with just an id, it'll default to clojure.test
thank you sir!