This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-07
Channels
- # announcements (1)
- # babashka (34)
- # bangalore-clj (2)
- # biff (2)
- # cider (63)
- # clj-commons (1)
- # clj-kondo (4)
- # cljdoc (44)
- # clojure (65)
- # clojure-europe (45)
- # clojure-nl (4)
- # clojure-norway (85)
- # clojure-uk (5)
- # clojurescript (5)
- # cursive (11)
- # datomic (8)
- # graalvm (11)
- # honeysql (7)
- # hoplon (9)
- # hyperfiddle (3)
- # introduce-yourself (1)
- # matrix (2)
- # missionary (17)
- # overtone (2)
- # polylith (6)
- # portal (16)
- # re-frame (24)
- # releases (2)
- # sci (45)
- # xtdb (9)
Hello. Is it possible to skip tests for a specific project?
Yes, I know there is a skip:proj argument, but we have a lot of small projects all depend on small set of common components and it's quite heavy to enumerate them all.
My idea right now is to install a default runner as a nullifying one.
You can specify :test {:include []} for a project in workspace.edn see https://cljdoc.org/d/polylith/clj-poly/0.2.18-SNAPSHOT/doc/testing#_include_and_exclude_bricks_by_configuration. Then no brick tests will be executed for that project.
Unfortunately, I can't say date. But the ambition is to release it this year. It will be a big release, but the idea is that it should be a good basis for the continued work. The goal is to release more frequently in the future.