On 8/20/20 12:17 PM, Lassi Kortela wrote:
> Whatever the reasons, a full-featured test definition framework is much simpler than a full-featured test runner.

It probably makes sense to split srfi-64 into multiple libraries, with the stuff for
writing test-runners in a separate library.

Also, in a Scheme that has some kind of class/interface inheritance
(or Haskell-style classes) it would no doubt be cleaner to
define test-runner as an abstract class/interface, along
with a default implementation.  Instead of using procedures to
replace the various hooks, you'd use inheritance to override them.

(Similar to custom ports.)
--
	--Per Bothner
xxxxxx@bothner.com   http://per.bothner.com/