This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-11
Channels
- # announcements (16)
- # aws (17)
- # babashka (25)
- # beginners (60)
- # calva (40)
- # cider (3)
- # clara (4)
- # clj-kondo (24)
- # clojure (16)
- # clojure-austin (3)
- # clojure-dev (23)
- # clojure-europe (33)
- # clojure-nl (2)
- # clojure-norway (7)
- # clojure-uk (4)
- # clojurescript (39)
- # clr (108)
- # conjure (10)
- # cursive (12)
- # datalevin (7)
- # editors (2)
- # events (1)
- # fulcro (24)
- # graalvm (3)
- # introduce-yourself (8)
- # london-clojurians (2)
- # malli (18)
- # meander (6)
- # missionary (10)
- # nbb (16)
- # off-topic (19)
- # polylith (1)
- # portal (4)
- # rdf (1)
- # reitit (4)
- # remote-jobs (3)
- # shadow-cljs (10)
- # xtdb (12)
We're looking at how we run different styles of tests with poly test from our build pipeline - we're using polylith-kaocha, and there is https://github.com/imrekoszo/polylith-kaocha/issues/6 about passing cli args, but there's a broader question for me which relates to how do people work with integration and smoke tests being run in a pipeline where you use docker-compose to mock other services (eg a database). we'd essentially want to do something like poly test :unit then later (when we run the associated services) poly test :integration - but at the moment, we can't even pass the cli argument to the kachoa wrapper. Curious how others who use polylith are working with build pipelines and integration tests, etc ? One thing we're thinking about is writing our own kaocha wrapper and using the output of ws:get-changed to run more complex tests at the brick level (and leave poly test to just run unit tests)