Hmmm. Looked at your test code. Basically, you want to know if when the code is executed, it didn't raise an exception. That wouldn't be terribly hard to do -- EXCEPT that when you call the assertion program, you would have to pass the call to the procedure as a STRING:

BEGIN
utassert.runsOK ('checksum.calc');

otherwise, the "argument" which is the call to checksum.calc will be evaluated before passing it to runsOK and an exception will be raised and so the assertion program will never actually be run. See what I mean?

For a simple no parm function like the above, this is no big deal, but when you have to concat in params, YUCH!

This is probably an example where offering more options and flexibility on GENERATION o the test package would come in much more handy, and I will record it as an enhancement that way!

Does this make sense?

SF