This is the ptester Reference Manual, generated automatically by Declt version 4.0 beta 2 "William Riker" on Sun Sep 15 06:25:30 2024 GMT+0.
The main system appears first, followed by any subsystem dependency.
ptester
Portable test harness package
Kevin M. Rosenberg <kmr@debian.org>
Kevin Layer, Franz, Inc / Kevin Rosenberg
LLGPL
ptester is a portable testing framework based on Franz’s tester module
src.lisp
(file).
Files are sorted by type and then listed depth-first from the systems components trees.
ptester/src.lisp
ptester
(system).
*break-on-test-failures*
(special variable).
*error-protect-tests*
(special variable).
*test-errors*
(special variable).
*test-successes*
(special variable).
*test-unexpected-failures*
(special variable).
test
(macro).
test-error
(macro).
test-no-error
(macro).
test-no-warning
(macro).
test-warning
(macro).
with-tests
(macro).
*announce-test*
(special variable).
*warn-cookie*
(special variable).
conditionp
(generic function).
errorset
(macro).
gc-print-state
(function).
(setf gc-print-state)
(function).
if*
(macro).
if*-keyword-list
(special variable).
simple-break
(condition).
test-check
(function).
test-values
(macro).
test-values-errorset
(macro).
Packages are listed by definition order.
ptester
common-lisp
.
*break-on-test-failures*
(special variable).
*error-protect-tests*
(special variable).
*test-errors*
(special variable).
*test-successes*
(special variable).
*test-unexpected-failures*
(special variable).
test
(macro).
test-error
(macro).
test-no-error
(macro).
test-no-warning
(macro).
test-warning
(macro).
with-tests
(macro).
*announce-test*
(special variable).
*warn-cookie*
(special variable).
conditionp
(generic function).
errorset
(macro).
gc-print-state
(function).
(setf gc-print-state)
(function).
if*
(macro).
if*-keyword-list
(special variable).
simple-break
(condition).
test-check
(function).
test-values
(macro).
test-values-errorset
(macro).
Definitions are sorted by export status, category, package, and then by lexicographic order.
When a test failure occurs, common-lisp:break is called, allowing interactive debugging of the failure.
Protect each test from errors. If an error occurs, then that will be taken as a test failure unless test-error is being used.
The value is the number of test errors which have occurred.
The value is the number of test successes which have occurred.
The value is the number of unexpected test failures which have occurred.
Perform a single test. ‘expected-value’ is the reference value for the
test. ‘test-form’ is a form that will produce the value to be compared to
the expected-value. If the values are not the same, then an error is
logged, otherwise a success is logged.
Normally the comparison of values is done with ‘eql’. The ‘test’ keyword
argument can be used to specify other comparison functions, such as eq,
equal,equalp, string=, string-equal, etc.
Normally, only the first return value from the test-form is considered,
however if ‘multiple-values’ is t, then all values returned from test-form
are considered.
‘fail-info’ allows more information to be printed with a test failure.
‘known-failure’ marks the test as a known failure. This allows for programs that do regression analysis on the output from a test run to discriminate on new versus known failures.
Test that ‘form’ signals an error. The order of evaluation of the
arguments is keywords first, then test form.
If ‘announce’ is non-nil, then cause the error message to be printed.
The ‘catch-breaks’ is non-nil then consider a call to common-lisp:break an
‘error’.
‘fail-info’ allows more information to be printed with a test failure.
‘known-failure’ marks the test as a known failure. This allows for
programs that do regression analysis on the output from a test run to
discriminate on new versus known failures.
If ‘condition-type’ is non-nil, it should be a symbol naming a condition
type, which is used to check against the signalled condition type. The
test will fail if they do not match.
‘include-subtypes’, used with ‘condition-type’, can be used to match a
condition to an entire subclass of the condition type hierarchy.
‘format-control’ and ‘format-arguments’ can be used to check the error message itself.
Test that ‘form’ does not signal an error. The order of evaluation of
the arguments is keywords first, then test form.
If ‘announce’ is non-nil, then cause the error message to be printed.
The ‘catch-breaks’ is non-nil then consider a call to common-lisp:break an
‘error’.
‘fail-info’ allows more information to be printed with a test failure.
‘known-failure’ marks the test as a known failure. This allows for programs that do regression analysis on the output from a test run to discriminate on new versus known failures.
Test that ‘form’ does not signal a warning. The order of evaluation of
the arguments is keywords first, then test form.
‘fail-info’ allows more information to be printed with a test failure.
‘known-failure’ marks the test as a known failure. This allows for programs that do regression analysis on the output from a test run to discriminate on new versus known failures.
Test that ‘form’ signals a warning. The order of evaluation of
the arguments is keywords first, then test form.
‘fail-info’ allows more information to be printed with a test failure.
‘known-failure’ marks the test as a known failure. This allows for programs that do regression analysis on the output from a test run to discriminate on new versus known failures.
Jump to: | (
C E F G I M T W |
---|
Jump to: | (
C E F G I M T W |
---|
Jump to: | *
I S |
---|
Jump to: | *
I S |
---|
Jump to: | C F P S |
---|
Jump to: | C F P S |
---|