This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-15
Channels
- # arachne (6)
- # aws-lambda (3)
- # beginners (14)
- # boot (56)
- # cider (8)
- # cljs-dev (5)
- # cljsrn (11)
- # clojure (240)
- # clojure-dusseldorf (3)
- # clojure-greece (165)
- # clojure-italy (5)
- # clojure-romania (1)
- # clojure-russia (24)
- # clojure-uk (30)
- # clojure-ukraine (3)
- # clojurescript (29)
- # core-async (6)
- # css (1)
- # cursive (25)
- # datascript (6)
- # datomic (61)
- # dirac (1)
- # events (3)
- # hoplon (1)
- # instaparse (3)
- # jobs (4)
- # juxt (28)
- # lein-figwheel (7)
- # leiningen (19)
- # luminus (1)
- # lumo (2)
- # nyc (1)
- # off-topic (19)
- # om (25)
- # onyx (4)
- # parinfer (2)
- # pedestal (23)
- # perun (20)
- # re-frame (44)
- # reagent (20)
- # remote-jobs (3)
- # ring (3)
- # ring-swagger (5)
- # rum (12)
- # slack-help (3)
- # spacemacs (25)
- # specter (62)
- # sql (16)
- # unrepl (313)
- # yada (4)
Morning
Bore da
morning
How slow are the tests in your current project? Mine are taking more than an hour to run the full suite locally!
our full CI test suite, including provisioning a DB, migrating it, and running tests takes around 10 mins... if i run locally it's about 7 or 8 mins, the bulk of that is a couple of individual tests which create large sets of objects in the db and test those sets are handled consistently, and a fair bit in clojure startup times because the project is split into modules
That's a good idea thanks. The reason I'm asking about test time is that I'm working for the first time in a project where tests are almost unusable. And discovering the codebase without relying on tests is a pain.
yeah, if having a fast test suite isn’t made a concrete goal, it generally becomes slow and annoying IME
kevin42 I'd suggest starting at the equivalent of the system if it exists, and see how the project has hierarchy. Then investigate the smaller "supporting" components first. From there move onto the major components.
@kevin42 Sorry I meant "system, or it's equivalent". Basically going via the component system if it exists.
No worries, thanks to you. The system tries to load the whole app and does not try to load some on demand (like a queue system).
Morning 👋