This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-30
Channels
- # adventofcode (22)
- # announcements (7)
- # beginners (32)
- # calva (56)
- # cider (96)
- # cljdoc (7)
- # cljs-dev (50)
- # clojure (173)
- # clojure-austin (8)
- # clojure-brasil (7)
- # clojure-europe (10)
- # clojure-greece (2)
- # clojure-italy (10)
- # clojure-nl (9)
- # clojure-spec (18)
- # clojure-uk (143)
- # clojurebridge (3)
- # clojurescript (9)
- # cursive (14)
- # data-science (1)
- # datascript (4)
- # datomic (9)
- # docker (7)
- # emacs (2)
- # figwheel-main (4)
- # fulcro (18)
- # garden (1)
- # graphql (13)
- # hyperfiddle (4)
- # juxt (2)
- # off-topic (43)
- # pathom (1)
- # pedestal (17)
- # portkey (163)
- # re-frame (4)
- # reitit (7)
- # rum (4)
- # shadow-cljs (139)
- # spacemacs (5)
- # sql (14)
- # unrepl (2)
Can anyone explain how to setup a repl for clojurescript using prepl. I'm interested to see what rebl can do based on... https://twitter.com/swannodette/status/1068224062835572739
Apparently you just need to load an additional jar, https://github.com/cognitect-labs/REBL-distro/blob/master/README.md
According to the testing docs:
By default, these functions will search for all tests defined in
a namespace and run them in an undefined order.
Is anyone aware of a way in which I could make tests in clojurescript run in a fixed order without using test-ns-hook
or doing everything manually? (from the docs it seems like test-ns-hook
and fixtures don’t play well together)
Using lein + doo and running on nodejs, if that makes any difference.other than manually setting it up with multiple (cljs.test/run-tests 'foo) (cljs.test/run-tests 'bar) ...
I imagined so… thanks @thheller!
You have probably already considered the possibility of taking the code that is currently spread across separate tests, and combine them into one test.
Yeah, I thought about that, but we’re using re-frame-test
and testing async code with run-test-async
, which means there can only be one call to it because of it calling (done)
. Joining everything inside a single test and working around that would probably be more trouble than just running the tests manually… Not to mention the nesting that we would have 😛
But thanks for the suggestion