I have begun looking into this one and found the following :

1) I was able to put a success message into the results
index by table by trapping success in utassert.eq as
shown here.

PROCEDURE this (
msg_in IN VARCHAR2,
check_this_in IN BOOLEAN,
null_ok_in IN BOOLEAN := FALSE,
raise_exc_in IN BOOLEAN := FALSE,
register_in IN BOOLEAN := TRUE
)
IS
BEGIN
IF utplsql.tracing
THEN
utplsql.pl ('utPLSQL TRACE on Assert: ' || msg_in);
utplsql.bpl (check_this_in);
END IF;

IF NOT check_this_in
OR ( check_this_in IS NULL
AND NOT null_ok_in)
THEN
IF register_in
THEN
utresult.report (msg_in);
ELSE
utplsql.pl (msg_in);
END IF;

IF showing_results AND register_in
THEN
utresult.showlast;
END IF;

IF raise_exc_in
THEN
RAISE test_failure;
END IF;

ELSE

/*
|| DRH : 20-DEC-2000
|| Report success as well as failure.
*/
utresult.report('I succeeded');

END IF;
END;

2) Unfortunately utresult bases success or failure on
the count of rows in the results index by table. So
I propose one of the following :

a) Add a field to the results index by table to denote
good results from bad and change the utresult package
to be aware of this.
b) Add a new index by table to denote good results and make
utresult aware of it.

Comments? Questions? Concerns?

Darryl Hurley
MDSI