Timothy Baldridge wrote:
I don't recommend Midje at all. Many of the framework's mocking
facilities (such as providing) are abominations.
Hacker News notwithstanding, "idiosyncratic interface" is not a synonym
for abomination.
It may look cute,
but I've lost countless hours to bugs and unexpected behavior related to
Midje.
An example would be handy right about now.
As the author of Midje, I protest. Lots of people use Midje for
production code without your problems. I've been using on production
code for coming on two years now.
C'mon: all of the main Clojure testing frameworks are opinionated, each
in different ways. They're all perfectly competent at what they do. They
don't hide bugs. They all have deterministic behavior. None of them are
all that complicated.
The pattern I do recommend is to break your system up into components.
Each component should be testable by mocking its dependencies and then
testing only that component. In a final test, stitch together all your
components and run system tests against all components at once.
I think this is good advice.
--
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
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
