This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-11
Channels
- # aleph (7)
- # announcements (5)
- # beginners (58)
- # calva (20)
- # cider (10)
- # clj-kondo (4)
- # cljfx (5)
- # cljsrn (7)
- # clojure (29)
- # clojure-europe (11)
- # clojure-mexico (1)
- # clojure-norway (26)
- # clojure-uk (9)
- # clojurescript (1)
- # cursive (31)
- # datahike (22)
- # datomic (12)
- # duct (3)
- # fulcro (28)
- # helix (35)
- # hyperfiddle (28)
- # lsp (4)
- # malli (8)
- # midje (3)
- # music (2)
- # nbb (9)
- # nrepl (20)
- # off-topic (36)
- # polylith (3)
- # shadow-cljs (47)
- # sql (2)
- # testing (7)
- # vim (17)
- # xtdb (7)
What do you mean by "verbose"?
Something along the lines of showing what tests inside the test file that are being run. I don’t have a clear vision of what I want, just more info regarding what’s happening - it depends on what is possible
Which test runner are you using with :test
- different test runners offer different options for that sort of thing.
It also sounds like you're interested in test coverage - showing which lines get tested. So perhaps look at cloverage
Have you looked at Kaocha @U033Q6RBXJ6? it's the most feature complete test runner for Clojure, and has multiple "reporters" that give you different kinds of output, as well as cloverage integration.
You can always define the multimethods yourself to make them more verbose. I actually do that in a few projects, if you're interested (on my work I'm currently redirecting the test output to Android emulator, for example)