Re: XCVB, a replacement for ASDF

> 2.  The test operation's semantics are unclear.  What should happen when
> one tests a component?  What is the contract the implementer should be
> making with user of the test system?  Should the test operation hurl
> errors?  It cannot return values.  Should it write output somewhere for
> later inspection?  If so, where should that output be written?  Ideally,
> we should find a contract that would accommodate the use of many
> different testing frameworks.


i have these all around in my systems:

(defmethod operation-done-p ((op test-op) (system (eql (find-system
:cl-rdbms))))
  nil)

about return values from operation: stefil is our test system. it's
basically a defun* that generates instrumented defuns that ensure a
test environment, plus some operators that record info in this env.
when you start such a defun, it'll mix in the collected test
environment as an nth+1 value into the return values. this is a clos
object that has a customized slime inspector...

so stefil pretty much relies on return values and currently i often
C-c C-c the test-op, and start the tests from the repl, only to be
able to inspect the test results at the end.

-- 
 attila

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/