| Allegro CL version 9.0 Moderate update since 9.0 release. 8.2 version |
Arguments: form &key announce catch-breaks fail-info known-failure
Test that form does not signal an error. The order of evaluation of the arguments is keywords first, then form.
If announce is non-nil, then cause the error message to be printed.
If the catch-breaks is non-nil then consider a call to common-lisp:break an error.
The value of the fail-info argument should be nil or a string. If a string, it is printed if the test fails, providing more information with a test failure. (Typical strings are "bug2127" and "can fail when network is slow".)
known-failure if true, affects what is printed when the test fails or succeeds. Thus a failure is reported as "Test failed: known failure: ..." and a success as "Expected test failure for [...] did not occur."
See test-harness.htm for information on the Allegro CL test harness.
Copyright (c) 1998-2019, Franz Inc. Oakland, CA., USA. All rights reserved.
This page was not revised from the 8.2 page.
Created 2012.5.30.
| Allegro CL version 9.0 Moderate update since 9.0 release. 8.2 version |