Matt Clark's test-expect library includes two versions of a report- problem function: a standalone version, and another that integrates with test-is. The comments suggest two ways to active the test-is version: wrapping calls to expect in a binding, and interning the specialized version of report-problem back into the main test namespace.
After playing with it for a few minutes, I decided I preferred the latter approach, and would suggest adding the following function to test-expect: (defn use-test-is! [] (require 'mdc.common.test-expect.test-is-adapter) (def report-problem (ns-resolve 'mdc.common.test-expect.test-is- adapter 'report-problem))) This feels a little hacky, but is there a better way? I don't see how binding/set! get me there, because I do not want to repeat bindings for every test, nor do I want to have to create a top level binding context. Stu --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
