This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-16
Channels
- # aws (17)
- # babashka (2)
- # beginners (131)
- # bristol-clojurians (1)
- # calva (16)
- # chlorine-clover (6)
- # cider (10)
- # clara (5)
- # cljsrn (82)
- # clojure (176)
- # clojure-dev (14)
- # clojure-europe (13)
- # clojure-italy (13)
- # clojure-nl (4)
- # clojure-spec (10)
- # clojure-sweden (32)
- # clojure-uk (32)
- # clojuredesign-podcast (2)
- # clojurescript (34)
- # community-development (2)
- # conjure (17)
- # cursive (4)
- # datomic (51)
- # emacs (6)
- # figwheel-main (26)
- # fulcro (16)
- # graalvm (11)
- # jobs (2)
- # jobs-discuss (30)
- # kaocha (4)
- # meander (23)
- # off-topic (34)
- # pathom (5)
- # re-frame (10)
- # reagent (3)
- # reitit (6)
- # releases (3)
- # sci (36)
- # shadow-cljs (27)
- # sql (9)
- # testing (6)
- # tools-deps (28)
- # vim (8)
Is there a known thing in clojure.test that the *ns*
is bound to user
? I’m trying to use a macro to generate temp databases that are unique to the namespace and it seems that both Kaocha and cognitect/test-runner will set the namespace to user
, probably doing the test discovery phase?
Huh, when you require
a namespace, the *ns*
var is not set to the “required” namespace, but stays to user…
(for folks here who are not in #clojure-dev that discussion shifted there and was answered -- TL;DR: it's the intended behavior)
Yeah I think I should delete the noise? I started from kaocha, shifted to testing after I tried cognitect/test-runner, then to clojure-dev with the root repro
Your call. I just wanted to tie up the loose end that the posts seem to be. 🙂