This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-25
Channels
- # announcements (4)
- # babashka (58)
- # beginners (21)
- # calva (42)
- # clj-kondo (15)
- # cljdoc (16)
- # cljs-dev (11)
- # clojure (57)
- # clojure-denmark (1)
- # clojure-europe (24)
- # clojure-france (4)
- # clojure-nl (1)
- # clojure-norway (16)
- # clojure-spec (6)
- # clojure-uk (2)
- # clojurescript (19)
- # clr (4)
- # conjure (1)
- # core-logic (3)
- # cursive (5)
- # data-science (2)
- # datascript (6)
- # datomic (3)
- # emacs (4)
- # events (3)
- # fulcro (17)
- # gratitude (2)
- # hyperfiddle (4)
- # introduce-yourself (3)
- # jobs-discuss (2)
- # lsp (27)
- # malli (22)
- # pathom (73)
- # portal (21)
- # re-frame (5)
- # releases (1)
- # vim (8)
- # xtdb (28)
Tried to take RCF for a spin today and I had some issues with its behavior when generating a test. I wrote a failing case, lein test didn't report it as a failure, and when I used cider-run-loaded-tests
it reported it ran it as a test function but it didn't fail
From reading the documentation and skimming the source I'd expect it to behave like any other test I defined with deftest
assuming *generate-tests*
was true
it sounds like a configuration or classpath issue out of band of RCF to me, do we know how lein test
detects tests and what cider-run-loaded-tests
does? they may have restrictions on file naming conventions and folder placement that RCF ignores
Can you confirm if this entrypoint style works:
{:aliases {:test {:jvm-opts ["-Dhyperfiddle.rcf.generate-tests=true"]}}}
clj -M:test -e "(require 'example)(clojure.test/run-tests 'example)"