On Thu, 7 Oct 1999 15:47:30 +1000 (GMT+1000), Allan Rae wrote:
>
>Unit-testing is certainly a good thing -- tests all those promises the
>code makes and keeps Arndt happy about programming by contract since the
>interface can't change without everybody finding out.
I've learned my suggestions are damn dangerous ;-)
For starters I'd propose only some very simple assert() macros to
become obligatory for public functions, testing arguments/globals
(preconditions) and return values/side effects (postconditions) for
obvious non-sense. Moreover each public method should document these
conditions (and what it is supposed to do, por supuesto).
Else we would found the 'HardCore testing LyX never come to terms
gang', making Core Developers live impossible.
Then the real testing experts can by and by implement the rest on their
own account and risk and report the results.
AH
