Folks, tl;dr -- https://github.com/jeaye/orchestra
I'd like to announce the release of Orchestra, which tackles an opinionated issue of clojure.spec's instrumentation not checking :ret and :fn specs. For those who side against the decision to elide those checks, I encourage you to drop Orchestra in, with nothing but a (:require) change. In my development, since making Orchestra, _every error_ I've seen has been a spec error. Compared to an accidental nil somewhere, in new, untested code, which trickled into some other place before rearing its head, spec errors are superb. My workflow has since become oriented around writing specs for functions as I write those functions and then knowing, since I'm instrumenting, whenever I use it incorrectly (ever so often). Note that I'm not suggesting that Orchestra should replace the need for unit tests, or spec's generative testing, or any other form of test writing outside the scope of just running your application. Since test writing often happens after the fact, however, in between sprints or otherwise, Orchestra provides a stern look at your data as it passes through your Clojure machine. Best, Jeaye -- 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.
signature.asc
Description: PGP signature
