Re: Suggestion for ASDF:TEST-OP

Robert Goldman wrote:
> 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

Sorry, this dropped somehow; should have been

The person writing the test-op would know to write his/her test report
to the result stream.  The easy backward compatible choice would be to
just bind *standard-output* to that for the duration of the test-op, but
better would be to isolate the report-writing components, and fix them
to use this stream.  Most test frameworks should be readily able to do this.



-------------------------------------------------------------------------
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/