diff options
| author | Arun Isaac | 2023-10-09 14:56:17 +0100 |
|---|---|---|
| committer | Arun Isaac | 2023-10-09 20:32:39 +0100 |
| commit | de18ef6d55b52f52837395684e6b8265b2ad26b3 (patch) | |
| tree | 379206c34a321b4f50fa21fef40d9ab4cff5bb90 /doc/echo.cwl | |
| parent | 7dbe776cb56803d9c66a847f5ac3613366754838 (diff) | |
| download | ccwl-de18ef6d55b52f52837395684e6b8265b2ad26b3.tar.gz ccwl-de18ef6d55b52f52837395684e6b8265b2ad26b3.tar.lz ccwl-de18ef6d55b52f52837395684e6b8265b2ad26b3.zip | |
tests: Catch expressions that don't raise exceptions.
Many tests that use guard to catch and ensure that certain conditions
are raised actually leak and let through cases where the expressions
result in a truthy value.
* tests/ccwl.scm ("input, when passed more than one positional
argument, must raise a &ccwl-violation condition", "input, when passed
an unrecognized keyword, must raise a &ccwl-violation condition",
"input, when passed multiple arguments to a unary keyword, must raise
a &ccwl-violation condition", "output, when passed more than one
positional argument, must raise a &ccwl-violation condition", "output,
when passed an unrecognized keyword, must raise a &ccwl-violation
condition", "output, when passed multiple arguments to a unary
keyword, must raise a &ccwl-violation condition", "command, when
passed positional arguments, must raise a &ccwl-violation condition",
"command, when passed an unrecognized keyword, must raise a
&ccwl-violation condition", "command, when passed multiple arguments
to a unary keyword, must raise a &ccwl-violation condition"): Catch
expressions that don't raise exceptions.
Diffstat (limited to 'doc/echo.cwl')
0 files changed, 0 insertions, 0 deletions