This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-03
Channels
- # adventofcode (1)
- # beginners (76)
- # boot (88)
- # cider (63)
- # clojure (357)
- # clojure-austin (2)
- # clojure-berlin (8)
- # clojure-brasil (8)
- # clojure-nl (1)
- # clojure-russia (22)
- # clojure-spec (17)
- # clojure-uk (47)
- # clojurescript (67)
- # cursive (45)
- # datascript (3)
- # datomic (45)
- # dirac (7)
- # emacs (3)
- # funcool (2)
- # hoplon (26)
- # jobs (2)
- # jobs-discuss (11)
- # luminus (6)
- # off-topic (243)
- # om (40)
- # om-next (7)
- # onyx (23)
- # overtone (1)
- # portland-or (2)
- # protorepl (11)
- # re-frame (55)
- # reagent (58)
- # rum (12)
- # sql (4)
- # test-check (12)
- # untangled (25)
This is all about faster feedback?
Sometimes I wish we had better tools for running a few choice tests to get fast feedback, and doing the heavy PBT via some async workflow
It might be possible to optimize the string/keyword generators by avoiding the intermediate vectors. Would be interesting to try, and would speed up a lot of people's tests if it works
when 100 iterations of tests takes 10 minutes versus 30 seconds, I think that goes beyond "faster feedback"
test.chuck has a mechanism for varying how many tests are run
@mattly is this jvm or js? I'll probably do some profiling