Suggestion for ASDF:TEST-OP

Something that's long bothered me about the test-op is that the
programmer who "consumes" it doesn't know what to do with the results of
running it, and the programmer who writes code for it doesn't know what
to do, either.

Here's a tentative proposal for extension:

Add to the test-op a test-result-stream slot and initarg (this is a
*tentative* proposal --- if it were to be approved, someone should come
up with something less verbose) that would default to t.

Explicitly declare that the test results should be written to this stream.

Having a protocol like this would make it easier for people running
tests to see how the tests ran, rather than having to guess what the
test writer intended, and without having to visually disentangle the
test results from random other bits that show up in standard output
(compiler warnings, etc.).  The person running the test-op could

This is just a tentative suggestion, but I hope that it's worth some
discussion and refinement on this discussion list.

best,
R



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/