> What are the cons of using midje? Any reason I shouldn't migrate all
> my unit testing to it?
I'm biased, but I think Midje is ready for production use. There's a smooth
migration path because Midje uses the same reporting as clojure.test, so you
can mix styles in the same file and still use (for example) lein test to see if
anything failed. (I'll go write up a Migrating page in the wiki after I send
this mail.)
There are things clojure.test does that Midje doesn't:
* Named tests (deftest). So you can't write runner functions like this:
(deftest arithmetic-tests
(subtraction-tests)
(addition-tests))
unless you also :use clojure.test and wrap the Midje facts in deftests (which
works fine).
* There's no equivalent to with-test.
* There's no #'are, though I suspect using checker functions would work as well.
Midje isn't a superset of the features of other clojure.test alternatives. For
example, it doesn't have the auto-runner that LazyTest does, and it doesn't
have the trimmed stack traces of Expectations. I plan to keep stealing ideas,
though.
-----
Brian Marick, Artisanal Labrador
Contract programming in Ruby and Clojure
Author of /Ring/ (forthcoming; sample: http://bit.ly/hfdf9T)
www.exampler.com, www.exampler.com/blog, www.twitter.com/marick
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
