Hello Stuart,
On 18 Nov., 15:58, Stuart Sierra <[EMAIL PROTECTED]> wrote:
> 1. I want to keep optional messages per-assertion. These are very
> useful in the RSpec testing framework for Ruby; they're like comments
> explaining what each assertion is supposed to demonstrate.
I'd also like to see the messages included. I'm working on a TAP
implementation for Clojure, which I find nice for communicating test
results to external processes. In TAP also the messages are used
as some kind of documentation.
This leads me to another question: Is it possible to look into
pluggable
harnesses? That is: can we separate the tests from the result
reporting?
In my TAP implementation I currently have two harnesses, one
produces TAP output, one can be used inside a test to allow recursive
tests. One application is for example the ClojureCheck library I am
working on.
(holds?
(for-all [x Integer
y Integer]
(is (= (+ x y) (+ y x))))
"addition commutes")
for-all sets up a batch-harness, so the body of the for-all may
contain
any number or form of tests. The result of the for-all, is then the
result
of the internal tests.
> 2. The current 'is' macro works more or less like the one Meikel
> described. The multimethod is "assert-expr", but it's complicated and
> could be simplified.
My sketch was rather minimalistic. I will post a more complete
example with working code later on today.
Sincerely
Meikel
--~--~---------~--~----~------------~-------~--~----~
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
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---
