#11 Improved error detection in generated test stubs.

[Mark Gawler]

It can be difficult to spot when the an typo is made in
the name of a stubbed subprogram.

With Set_Value / Get_value it is reasonably obvious as
a STUBS.NO_VALUE exception is raised, although this can
be tedious to track down. With Number_Of_Calls there is
no indication except zero is always returned, which if
your testing for zero calls you wont spot!

[Simon Wright]

Logged In: YES
user_id=917025

This seems like an excellent plan!

[Simon Wright]

Logged In: YES
user_id=917025

Logged as CF bug 0321.

[Simon Wright]

Logged In: YES
user_id=917025

Logged as CF bug 0321.

[Simon Wright]

Logged In: YES
user_id=917025

It would also be a good idea to check for accidental overriding of an
already-set value; (eg, if the setup says the first call should return 42 and
you alter this in the test procedure). The present code does the wrong
thing; it ignores the problem and uses the previous value!