![]() [It will not bother me if we revert this commit. I liked SK's idea and found it easy to implement. I wonder if others will be worried that it is easy to unintentionally leave off the second argument to check-error. I also wonder if it is problematic to add new string constants, like I've done.] Here is an example: (check-error (/ 1 0) "/: division by zero") (check-error (/ 1 0) "divide by zero") (check-error (/ 1 0)) (check-error 1) Here is the output: Ran 4 tests. 2 of the 4 tests failed. No signature violations. Check failures: check-error encountered the following error instead of the expected divide by zero :: /: division by zero in ex.rkt, line 2, column 0 check-error expected an error, but instead received the value 1. in ex.rkt, line 4, column 0 |
||
---|---|---|
.. | ||
aligned-pasteboard | ||
compiler | ||
data | ||
datalog | ||
deinprogramm | ||
drracket | ||
file | ||
framework | ||
frtime | ||
future | ||
gracket | ||
honu | ||
htdp-lang | ||
html | ||
jpr | ||
lazy | ||
macro-debugger | ||
match | ||
mysterx | ||
mzcom | ||
net | ||
plai | ||
planet | ||
plot | ||
profile | ||
r6rs | ||
racket | ||
racklog | ||
rackunit | ||
scribble | ||
slatex | ||
srfi | ||
srpersist | ||
stepper | ||
stxparse | ||
syntax-color | ||
test-engine | ||
typed-scheme | ||
units | ||
unstable | ||
utils | ||
web-server | ||
xml | ||
eli-tester.rkt | ||
info.rkt | ||
run-automated-tests.rkt | ||
stress.rkt | ||
zo-size.rkt |