Timothy Baldridge wrote:
I assert that a simpler library, something that only provides deftest,
assert and run-tests forces developers to think about the best way to
test something, and to write their own macros (as patterns emerge)
A not-unreasonable idea. Midje supports that by also running
clojure.test tests, making it easy to migrate when you get tired of
writing your own functions to compare expected to actual results in
different ways.
It's also reasonable to simply not use the mocking parts of Midje (or
other frameworks). Then you'll have clojure.test with a syntax you may
hate or like, plus more checker functions. The documentation since 1.5
should make that easy.
--
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.
