Next: SRFI-64 Test Results, Previous: SRFI-64 Conditonal Test Suites and Other Advanced Features, Up: SRFI-64: A Scheme API for Test Suites [Contents][Index]
A test-runner is an object that runs a test-suite, and manages the state. The test group path, and the sets skip and expected-fail specifiers are part of the test-runner. A test-runner will also typically accumulate statistics about executed tests,
True if and only if value is a test-runner object.
Get or set the current test-runner.
Same as (test-runner-current), but throws an exception if there
is no current test-runner.
Creates a new simple test-runner, that prints errors and a summary on the standard output port.
Creates a new test-runner, that does nothing with the test results. This is mainly meant for extending when writing a custom runner.
Create a new test-runner. Equivalent to ‘((test-runner-factory))’.
Get or set the current test-runner factory. A factory is a
zero-argument function that creates a new test-runner. The default
value is test-runner-simple.
Calls procedure with no arguments using the specified runner
as the current test-runner. If runner is omitted, then
(test-runner-current) is used. (If there is no current runner,
one is created as in test-begin.) If one or more
specifiers are listed then only tests matching the
specifiers are executed. A specifier has the same form as
one used for test-skip. A test is executed if it matches any of
the specifiers in the test-apply and does not match
any active test-skip specifiers.
Executes each decl-or-expr in order in a context where the current test-runner is runner.