This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-04
Channels
- # announcements (28)
- # asami (12)
- # aws (3)
- # babashka (69)
- # babashka-sci-dev (34)
- # beginners (52)
- # biff (3)
- # calva (20)
- # clj-kondo (4)
- # cljsrn (4)
- # clojars (1)
- # clojure (90)
- # clojure-czech (2)
- # clojure-europe (33)
- # clojure-nl (11)
- # clojure-norway (35)
- # clojure-seattle (1)
- # clojure-uk (5)
- # clojurescript (87)
- # cursive (10)
- # datascript (5)
- # datomic (35)
- # defnpodcast (1)
- # emacs (8)
- # events (4)
- # fulcro (1)
- # google-cloud (2)
- # graphql (2)
- # hispano (2)
- # honeysql (5)
- # hoplon (2)
- # hugsql (1)
- # jobs (7)
- # kaocha (9)
- # lsp (102)
- # meander (13)
- # observability (7)
- # off-topic (56)
- # overtone (2)
- # pathom (47)
- # podcasts-discuss (1)
- # rdf (30)
- # reagent (16)
- # reitit (1)
- # releases (2)
- # remote-jobs (26)
- # rewrite-clj (10)
- # tools-deps (4)
- # vim (5)
- # vscode (4)
- # xtdb (41)
Hey guys, there's something that confused me a bit when working with kaocha-cljs2. So i set up the whole thing including funnel with shadow, but what's weird is i noticed i can run my tests without using funnel, but also when i use funnel with -vv
I can see in the logs when i run my tests. What's actually going ion?
I don't have an explicit dependency on chui but yes, using chui with the gui interface.
yeah in that case Chui can run standalone, so if you mean you are "running tests" from the GUI then that's what's happening
The way to think about this is that there's a ClojureScript "headless" test runner, namely chui-core. This is just an API, it doesn't do much by itself. Chui-ui provides a browser-based UI. Kaocha-cljs2 provides a CLI interface, by remote controlling chui-core via chui-remote+funnel
@U07FP7QJ0 I see, thanks for the explanation. Sorry for cross-posting, I don't know whether you're part of the lambdaisland team or not.
Hi there, can I set :bindings
per suite? or based on an env var?
My use case is to reduce test timeout when developing locally vs having a bigger timeout in CI
Oh ok I think I can use :profiles
for that actually