Comments on: Testing Clojure Code – Awesome “are” http://techbehindtech.com/2010/10/19/testing-clojure-code-awesome-are/ Raw information. No finesse :) Tue, 28 May 2013 06:47:19 +0000 hourly 1 http://wordpress.com/ By: Siva Jagadeesan http://techbehindtech.com/2010/10/19/testing-clojure-code-awesome-are/#comment-118 Tue, 19 Oct 2010 21:00:34 +0000 https://sivajag.wordpress.com/?p=205#comment-118 Yah Shantanu, I think it is worth it.

In fact, when it fails, it shows exactly which case failed.

expected: (= "2016-02-29 23:59" (date-to-string (end-of-month (date-from-string "2016-01-03 03:01"))))
actual: (not (= "2016-02-29 23:59" "2016-01-31 23:59"))

]]> By: Shantanu Kumar http://techbehindtech.com/2010/10/19/testing-clojure-code-awesome-are/#comment-117 Tue, 19 Oct 2010 20:08:55 +0000 https://sivajag.wordpress.com/?p=205#comment-117 This is neat. But the documentation for ‘are’ says it may break error messages (line number reporting). Still worth it?

]]>