This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-15
Channels
- # aleph (14)
- # aws (5)
- # beginners (144)
- # bitcoin (1)
- # boot (14)
- # chestnut (13)
- # cljs-dev (58)
- # cljs-experience (1)
- # cljsrn (47)
- # clojure (107)
- # clojure-dev (9)
- # clojure-finland (12)
- # clojure-gamedev (4)
- # clojure-russia (2)
- # clojure-sanfrancisco (1)
- # clojure-spec (5)
- # clojure-uk (28)
- # clojurescript (34)
- # cursive (9)
- # datomic (3)
- # emacs (11)
- # garden (16)
- # graphql (9)
- # hoplon (3)
- # jobs (2)
- # juxt (6)
- # off-topic (32)
- # om (10)
- # onyx (1)
- # pedestal (4)
- # proton (1)
- # re-frame (14)
- # reagent (8)
- # ring (1)
- # ring-swagger (34)
- # shadow-cljs (19)
- # sioux-falls (1)
- # spacemacs (16)
- # testing (14)
Have you checked out https://github.com/clojure/test.check ?
the company I work for currently uses Midje so I gotta work on not only getting better at writing tests in Clojure generally, but on Midje specifically
Lots of people will advise you against using Midje...
@seancorfield curious as to why btw? I’ve never taken the time to learn it. I’ve always used test.check
test.check
can be used with Midje (and with clojure.test
and Expectations
) by the way. It adds functionality, it doesn't replace them.
@aj Midje is very macro-heavy and defines it's own (non-idiomatic) DSL on top of Clojure. Some people feel it has far too much "magic" in it.
yeah even internally there are complaints about using midje but I wasn’t here when the decision was made sooooo
@seancorfield thanks for the info! I’ll definitely spend some time learning it