Per Bothner <xxxxxx@bothner.com> writes:

> Do you have a plug-in replacement for Kawa's gnu/kawa/slib/testing.scm?
> I gather so, since you've tested it.

One is in the attachment.  I didn't note down the steps I had to take,
but from memory it should be roughly:

- concatenate the *.body.scm files in the order: test-runner, execution,
  source info, test-runner-simple,
- add "else" clauses to 'case' expressions,
- add "require" and module export boilerplate,
- define and export %test-begin as a synonym to test-begin,
- move some definitions to before their first use.

> One minor thing I noticed: The export list in test-runner.exports.sld
> exports a number of '%'-prefixed names.  These are supposed to be internal
> names that should probably *not* be exported.  I realize fixing this may
> require some re-organizing.

They're at least not exported from the master-library (srfi 64), and
it's only the execution module that uses the internal test-runner forms
(for which it makes sense to know more about test-runner internals than
a user), and not e.g. test-runner-simple (which is a test runner which a
user should be able to implement with the public API), so I don't find
it urgent, but I might look into it eventually.

A bit less nice might be that the simple test runner uses the log-file
and log-port fields of the test-runner record type.  Those fields are
non-standard and undocumented so far.  I'm not sure if I should document
them, make the simple test runner use its aux value field after all
(only when installed automatically, so instances returned from
(test-runner-simple) continue to be spec-conformant), or leave the
situation as it is.

Sub-typing of record types would have been handy here...

Taylan