This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-24
Channels
- # announcements (6)
- # babashka (25)
- # beginners (52)
- # cherry (8)
- # cider (9)
- # clj-kondo (9)
- # clojure (44)
- # clojure-australia (5)
- # clojure-dev (4)
- # clojure-europe (8)
- # clojure-nl (5)
- # clojure-norway (3)
- # clojure-spec (3)
- # clojure-uk (1)
- # clojurescript (16)
- # conjure (1)
- # core-async (8)
- # cursive (11)
- # fulcro (13)
- # honeysql (6)
- # hyperfiddle (13)
- # jackdaw (1)
- # jobs (9)
- # lsp (13)
- # meander (5)
- # missionary (2)
- # off-topic (11)
- # polylith (11)
- # re-frame (2)
- # reitit (11)
- # shadow-cljs (69)
- # squint (23)
- # tools-deps (30)
- # xtdb (3)
Hi folks. Is there any cider feature that requires following the convention of adding a -test
suffix to unit tests names?
I'm not aware of cider features that assume the convention -test
for deftests.
There is an assumption that the namespace ends in -test
to automatically infer test namespaces (configurable via https://docs.cider.mx/cider/testing/running_tests.html#test-namespace-naming-convention) and the macros that define tests (configurable via https://docs.cider.mx/cider/testing/running_tests.html#macros-used-to-define-tests)
not really, test runners and CIDER look at ^:test
metadata, as emitted by deftest and many other popular macros. So you can use whatever you please - I've never seen the opposite being an issue
cc/ @U976F1AR2
Thanks, folks.
In this case, any ideas on why there’s this convention of using -test
in test vars names? In principle, it would be redundant so I suppose there must be some good reason for it.