This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-17
Channels
- # adventofcode (25)
- # announcements (2)
- # babashka (16)
- # babashka-sci-dev (16)
- # beginners (213)
- # calva (15)
- # clj-kondo (126)
- # clj-on-windows (1)
- # cljdoc (5)
- # cljfx (1)
- # cljs-dev (6)
- # clojure (230)
- # clojure-europe (38)
- # clojure-nl (3)
- # clojure-uk (3)
- # conjure (10)
- # core-async (15)
- # cursive (33)
- # fulcro (58)
- # hyperfiddle (4)
- # jobs-discuss (1)
- # kaocha (5)
- # lsp (46)
- # meander (3)
- # off-topic (30)
- # polylith (10)
- # portal (9)
- # re-frame (5)
- # reitit (7)
- # releases (2)
- # ring (17)
- # sci (8)
- # shadow-cljs (6)
- # specter (1)
- # sql (1)
- # testing (9)
- # tools-deps (4)
- # vim (12)
I've started using RCF and I really like it, but I feel like I'm making a mess of my codebase just scattering tests
all over the place. Anyone using a test organizing strategy they could share?
You could organize them like clojure.test
tests. my_ns
for your implementation, my_ns_test
for tests.
core usage examples under the function; edge cases, regression tests and tests that need scaffolding can go in a test namespace (and fallback to clojure.test if needed); you can put _test files next to the primary ns where it is easily discovered bc there are no file watchers (though we haven't tried this pattern yet, let me know if there are problems)
can you say more about the mess you are seeing?