Thanks a lot, Phil! I agree with you because your soultion can be a good workaround. But I want to know the reason why the deftest- macro is not working as intended. Could you tell me why?
Did the developer of the deftest- macro write a incorrect code or am I wrong in understanding the prupose of the deftest- macro? On Nov 6, 5:33 am, Phil Hagelberg <p...@hagelb.org> wrote: > On Sat, Nov 5, 2011 at 6:57 AM, Young Kim <philo...@gmail.com> wrote: > > The unexpected result was that the message "Ran 5 tests containing 8 > > assertions". > > > The expected message was that "Ran 3 tests containing 4 assertions", > > because of two dertest- macros in my test code. > > > How can I block the execution of the two private deftest- macros in my > > test code? > > Just use defn instead of deftest-. There's no reason calls to "is" > can't occur in regular function bodies. > > -Phil -- 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
