This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-08-18
Channels
- # admin-announcements (59)
- # beginners (5)
- # boot (99)
- # cider (9)
- # clojure (207)
- # clojure-czech (1)
- # clojure-dev (28)
- # clojure-france (3)
- # clojure-italy (1)
- # clojure-japan (22)
- # clojurescript (234)
- # core-async (12)
- # datascript (1)
- # datomic (60)
- # funcool (137)
- # hoplon (18)
- # instaparse (2)
- # jobs (2)
- # ldnclj (42)
- # ldnproclodo (3)
- # liberator (13)
- # off-topic (21)
- # onyx (2)
- # re-frame (5)
- # reagent (12)
- # ring-swagger (5)
- # testing (17)
I basically use clojure.test (and cljs.test) and test.check (sometimes with sugar provided by test.chuck)
I feel they are more complex, and don't give much in return. They do so many things that I don't need most of the time. I can always use a macro to avoid some kind of repetition.
Oh, I also like humane-test-output to improve the output from clojure.test... And also juxt/iota
@nberger: same as you, but without expectations (no particular reason, I'm just content with clojure.test
)
@bensu: cool. Well, I'm not actually using expectations, it's just that from what I've seen, it seems less "invasive" than the others, so I could use it, but probably won't
I really liked juxt/iota, from @malcolmsparks , it's tasty sugar for clojure.test
One nice addition to juxt/iota would be to have a way to add a message on a certain assertion, so when it fails you can distinguish it from the others... it would be transformed to the 3-arity form of clojure.test/is
ah yes, that would be nice, I'll see about working that in
it's a bit of a pain right now when a particular triple fails, at least in my emacs I don't see a good indication of the triple that caused the failure