This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-28
Channels
- # announcements (3)
- # babashka (36)
- # beginners (77)
- # boot (3)
- # chlorine-clover (10)
- # cider (27)
- # clj-kondo (1)
- # cljs-dev (4)
- # clojure (256)
- # clojure-belgium (1)
- # clojure-europe (9)
- # clojure-uk (18)
- # clojuredesign-podcast (9)
- # clojurescript (54)
- # cryogen (8)
- # cursive (3)
- # data-science (1)
- # datomic (2)
- # duct (31)
- # events (1)
- # exercism (3)
- # fulcro (116)
- # joker (20)
- # kaocha (5)
- # meander (2)
- # nrepl (4)
- # off-topic (10)
- # other-languages (15)
- # re-frame (18)
- # reagent (4)
- # shadow-cljs (44)
- # sql (14)
- # tools-deps (17)
@plexus so I've still been struggling with this. I actually discovered that in --watch
mode, the value was initially unset, then gets set.
I've tried messing with wrap-run
and pre-run
/`post-run` instead now, still without success.
stepping back a bit, it feels like passing some configuration values (a port or URL, say) from the test runner's environment and command line into a test suite seems like a reasonable enough feature.
say, a field on a testable in tests.edn that's available at runtime to the tests. for that matter, why isn't the whole current test suite and test in atoms somewhere?
Hi! I am Garvita. I'm an RGSOC aspirant and look forward to contributing to this project. My team needs a coach. My teammate @larika18243 and I are based in India. Anyone working remotely is also okay. Please guide us further. Thank You 🙂