This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-14
Channels
- # announcements (10)
- # babashka (14)
- # beginners (51)
- # calva (2)
- # cider (28)
- # cljs-dev (1)
- # cljsrn (3)
- # clojure (185)
- # clojure-dev (15)
- # clojure-europe (6)
- # clojure-italy (2)
- # clojure-nl (6)
- # clojure-uk (45)
- # clojurescript (4)
- # conjure (12)
- # datomic (37)
- # duct (37)
- # figwheel-main (15)
- # helix (23)
- # interceptors (1)
- # jobs (1)
- # jobs-discuss (11)
- # jvm (5)
- # luminus (3)
- # malli (15)
- # off-topic (69)
- # pathom (8)
- # pedestal (2)
- # re-frame (7)
- # reagent (58)
- # reitit (33)
- # remote-jobs (1)
- # rum (14)
- # sci (7)
- # shadow-cljs (15)
- # spacemacs (9)
- # testing (19)
- # timbre (3)
- # tools-deps (14)
it is still quite hacky, and specific to rewrite-cljc needs, but here’s little sci-test experiment https://github.com/lread/sci-test
Here’s what I brought in from test.check https://github.com/lread/sci-test/blob/master/src/sci_test/impl/test_check.clj
Am temporarily using a fork of sci to get around that :line
issue I was talking about but will find some time to distill https://github.com/borkdude/sci/compare/master...lread:lread-line-meta
I’ll also hover back to clj-graal-docs and update testing strategies with this technique as another option.
The experiment taught me a bunch of stuff, but funny thing, I’m not sure I needed it. I had missed that I was not using Clojure direct linking in my original natively-compile-it-all tests. I have to do a test or two but I think this original strategy might fit under GitHub Actions 7gb RAM. But at least I am testing that I now work under sci!