   Copyright (C)  2000    Daniel A. Atkinson
   Copyright (C)  2004    Ivano Primi  <ivano.primi@tin.it>    

   Copying and distribution of this file, with or without modification,
   are permitted in any medium without royalty provided the copyright
   notice and this notice are preserved.

******************************************************************************

                        TESTING HPALIB

 Three script files, run_all_tests (a shell script), runtest (another shell
 script) and testex (a perl script) are supplied to facilitate comparison of 
 test program output with the sample output appended as a comment to each test
 source file. These scripts must be left in the 'test' subdirectory
 of the distribution source of the HPA library. 
 You should check the first line of each script and modify it if
 the locations assumed /bin/sh and /usr/bin/perl are not correct.
 You may also have to change the definition of the CC variable
 in run_all_tests and runtest if the name of your C compiler is not 'cc'
 or 'cc' does not work properly and you can use 'gcc' as alternative.
 
 To run all tests at once you have simply to execute run_all_tests in
 the 'test' subdirectory of the distribution source of the HPA library: 

       $  ./run_all_tests

 (here $ is the prompt of the shell ! :) )

 The standard command line parameters for each test are tabulated in the
 README file of the test/ subdirectory. This tabulation also specifies
 the sequence of prompt responses (if any) required to generate the
 standard test output. 
 
 The output resulting from the execution of each test program is 
 compared, using 'diff', to the standard output appended as a comment to the
 source file of the test program.

 If all tests succeed, then the output of run_all_tests should be

 :::::::::: t2xtrig.c  ::::::::::

 :::::::::: tatox.c    ::::::::::

 :::::::::: tbxprint.c ::::::::::

 :::::::::: tcform.c   ::::::::::

 :::::::::: tcxabs.c   ::::::::::

 :::::::::: tcxbasic.c ::::::::::

 :::::::::: tcxbin.c   ::::::::::

 ... (continue)

 Any differences in numerical values that appear may indicate a failed test.

     Note that some compilers generate slightly different formats for
 scientific (%e) notation, so differences in such numbers, flagged by 'diff',
 should be inspected to see if they actually differ in value as well as
 format.
