> is there a 'benefits over clojure.test' blog anywhere? Not that I’m aware of. I added a GH issue against the website content for that. Jay wrote a series of blog posts about Expectations back in 2011 that included the justification for it:
http://blog.jayfields.com/2011/11/clojure-expectations-introduction.html > I wonder if it is the benefits are more subjective Yes, I find the BDD-style of Expectations much more to my liking than the assertive style of clojure.test – the latter feels very imperative to me. So there’s definitely an element of stylistic preference at play here. > I personally like the names I give to tests etc. Jay has an opinion on that – see http://blog.jayfields.com/2011/11/clojure-expectations-unit-testing-wrap.html I’m split on the topic. There’s a practical reason for giving tests names, and that relates to tooling and, in particular, what CIDER and other tools expect (and in fact that is what has triggered this whole re-launching: in order to better support tooling at large, Expectations needs to provide a way to give predictable names to tests so that tooling can run and re-run individual tests). Sean -- 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.
