This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-09-20
Channels
- # announcements (3)
- # babashka (7)
- # beginners (43)
- # biff (19)
- # calva (39)
- # cider (16)
- # clerk (2)
- # clj-yaml (32)
- # cljs-dev (37)
- # clojure (129)
- # clojure-australia (1)
- # clojure-china (1)
- # clojure-europe (46)
- # clojure-filipino (1)
- # clojure-gamedev (25)
- # clojure-hk (1)
- # clojure-indonesia (1)
- # clojure-japan (2)
- # clojure-korea (1)
- # clojure-my (1)
- # clojure-nl (5)
- # clojure-norway (8)
- # clojure-sg (1)
- # clojure-sweden (12)
- # clojure-taiwan (1)
- # clojure-uk (9)
- # clojurescript (14)
- # core-typed (136)
- # cursive (18)
- # duct (9)
- # emacs (12)
- # etaoin (7)
- # events (1)
- # graalvm (3)
- # gratitude (2)
- # humbleui (7)
- # hyperfiddle (99)
- # introduce-yourself (5)
- # jobs (2)
- # leiningen (1)
- # missionary (14)
- # nrepl (2)
- # off-topic (12)
- # polylith (21)
- # rdf (29)
- # re-frame (8)
- # releases (1)
- # shadow-cljs (264)
- # spacemacs (21)
- # sql (7)
- # vscode (1)
is there a way to run either (a) kaocha code coverage (b) kaocha test suite (c) koacha watcher in https://github.com/imrekoszo/polylith-kaocha but not all at once, usually this is done via kaocha cli —with-profile
cloverage is supported by the project, there is example code for it as well https://github.com/search?q=repo%3Aimrekoszo%2Fpolylith-kaocha%20cloverage&type=code
cli args aren't currently supported either: https://github.com/imrekoszo/polylith-kaocha/issues/6
This project is not mature by any means, more like an mvp and since making it public I haven't had time to properly maintain it. Proceed with caution and expect roadblocks
I saw it was unmaintained, but from my tests, it worked surprisingly well. I don't think it need much maintenance work. > what do you mean by "not all at once"? In my kaocha EDN , i'll have multiple profiles setup like the screenshot
then execute
exec clojure ... -m kaocha.runner --config-file etc/kaocha/config.edn profile-name
in my current CICD setup, i need to be able to run -just- code coverage, or -just- unit tests
i'll see if i can find a workaround... but what I described is extremely common kaocha setups, and in their docs.
even just being able to pass KAOCHA_PROFILE on the command line, would probably work here.
would you accept a PR for environment variables? that's the path of least resistance here