On Nov 15, 2014, at 3:52 PM, Colin Yates <colin.ya...@gmail.com> wrote:
> For example, in the early days I was particularly susceptible to writing > functions which did too much and called too many other functions. With Midje, > mocking these other functions was trivial, on hindsight a bit more pain would > have been a helpful smell. I'm susceptible to that, too - still figuring it out. The terminology Midje uses, which is supposed to be reminiscent of facts that are true if subsidiary prerequisites/lemmas are, was intended to help. If the `prerequisite` or `provided` form says something interesting about the domain, it's more likely to be useful than if it's just something that makes the test easier to pass. After about a year and a half of daily use of Midje on production code, I'm finding my style is to be mock-heavy on early iterations, reducing the number as new requirements force rework of the tests and code. -------- Latest book: /Functional Programming for the Object-Oriented Programmer/ https://leanpub.com/fp-oo -- 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.
