What - expectations is a minimalist's testing framework - what you are testing is inferred from the expected and actual forms - stacktraces are trimmed of clojure library lines and java.lang lines - focused error & failure messages
Where - https://github.com/jaycfields/expectations When - read through this code and decide if you prefer these tests to the ones you're currently writing: https://github.com/jaycfields/expectations/blob/master/test/clojure/success/success_examples.clj Why - I prefer simple code that requires the minimum amount of ceremony. expectations has a very strong emphasis on removing as much noise as possible in the code itself and in the error messages that are presented when a failure occurs. When a test fails the framework concisely tells you what exactly went wrong and what it thinks is likely the problem. expectations also has a strong focus on consistency - whether you are testing equality, regex matching, expected exceptions, or interactions, the syntax remains the same. This leads to easy to write and easy to read tests - again, it's all about increasing signal and reducing noise. Stability - I've been using expectations to test prod code for over 2 years. If you'd like to get started with expectations, https://github.com/jaycfields/expectations contains instructions for getting started using Lein, Emacs, IntelliJ, or nothing at all. Cheers, Jay -- 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
