Re: New asdf version

Marco Baringer <[email protected]> writes:

> no matter what (if any) testing framework is chosen if someone does
> want to write a test suite it should be easy to run it through
> asdf. proposal:
>
> If you have a test suite define a method on the generic function
> asdf:test specialized to (eql <name of system>), ie:
>
> (defmethod asdf:test ((dummy (eql :my-system)))
>   (whatever)
>   ...)
>
> asdf:test-op will simply call the generic function asdf:test passing
> the system name as the first arg, this method should print out a
> message like "PASSED" or "FAILED", but isn't actually required to do
> anything. If no such method is found asdf will do nothing.

Perhaps I'm being dense, but what does this offer over

(defmethod asdf:perform ((o test-op) (c (eql (find-system 'my-system))))
  (do whatever))

in my-system.asd ?


[asdflint]
> well, the the code may be hard to check, but meeting certain ASDF
> requirements shouldn't be: something like a simple
> asdf-system-complaint-op which checks the existence of doc/index.html,
> the existence of a package named <system-name>.system, a defsystem
> form in the file <system-name>.asd, a directory with some tests,

Yes, something like that'd be a good start at least.


-dan

-- 

   http://www.cliki.net/ - Link farm for free CL-on-Unix resources 


-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink? 
You could win a Tablet PC. Get a free Tablet PC hat just for playing. 
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en