[asdf-devel] ASDF test-op question

[Daniel Herring]

On Mon, 5 Oct 2009, Robert Goldman wrote:
> Gary King wrote:
>> Hi Robert,
>>
>>> I don't believe that this is a general solution, for two reasons:
>>
>> I agree that it isn't a general solution especially since there is no
>> interface/API for clients to do anything with an ASDF operation! It
>> might, however, be a small step in the right direction.
>
> An alternative solution would be to provide a :stream or :filename init
> argument for the test-op operation class and bind a dynamic variable
> around every perform, making the stream or filename available for
> writing....

Why serialize the data?  Could we design a structured API to be used by 
other tools?

What if each test logged messages to asdf:*test-stream* and finished by 
calling
(asdf:test-result test-description-string result-keyword)

DejaGnu has a good description of test results; the keywords from good to 
bad could be :xpass, :xfail, :untested, :unresolved, :unsupported, :pass, 
and :fail.
http://www.gnu.org/software/dejagnu/manual/x47.html

Then asdf:test-op could return (values worst-result results-list).

Of course ASDF doesn't need to reinvent testing; there are plenty of 
existing frameworks to choose from.
http://www.cliki.net/test_framework


Later,
Daniel