Return to READ.ME CVS log

Up to [CSRG BSD Unix] / 43BSD / contrib / icon / libtest

Annotation of 43BSD/contrib/icon/libtest/READ.ME, revision 1.1.1.1

1.1       root        1: The tests in this directory are intended primarily in checking the Icon
                      2: program library for distribution and not for use by installers.
                      3: They are included in the distribution, however, since they might be helpful
                      4: if unexpected problems arise and they may give some insight into the
                      5: library.
                      6: 
                      7: There are three sections of tests: programs, procedures, and C functions.
                      8: The first two are done by
                      9: 
                     10:        make Prog
                     11:        make Proc
                     12: 
                     13: or by
                     14: 
                     15:        make All
                     16: 
                     17: which does both.
                     18: 
                     19: The program tests are in two parts. This is because some programs
                     20: require command-line arguments or produce data other than to standard
                     21: output.  The first part, done by the shell script Prog1test, handles
                     22: those programs that can be tested with a data file in standard input.
                     23: The second part, done by the shell script Prog2test, handles the
                     24: rest. These shell scripts work from .tlist files, which contain
                     25: program names.  In the case of Prog2test, the names correspond to
                     26: shell scripts, which have tailored tests.
                     27: 
                     28: The programs that test the procedure libraries include link directives
                     29: to access the ucode for the libraries (in ../ilib). All of these tests
                     30: work from standard input to standard output.
                     31: 
                     32: The C functions are tested as part of the personalized interpreter
                     33: test and are not done via the Makefile here. The shell script used
                     34: is Functest.
                     35: 
                     36: These tests are far from exhaustive -- they are only intended to
                     37: verify that the programs are at least functional.
                     38: 
                     39: The tests, like the others in the Icon Version 5.9 distribution,
                     40: compare locally generated output in local/*.out with corresponding
                     41: "standard" output in distr/*.out. The standard output was produced
                     42: on a VAX-11/780 running 4.2bsd.
                     43: 
                     44: The library includes programs, procedures, and functions that
                     45: are machine- and system-dependent.  Discrepancies between local
                     46: and distr output should be examined to determine if they are
                     47: due to such a dependency.  The library also uses both the sets
                     48: and experimental extensions in Version 5.9 (see TR 84-10).  If
                     49: these extensions are not included in the local installation,
                     50: some of the tests will fail prematurely.
                     51: 
                     52: There are two programs that probably will produce output
                     53: locally that is different from the standard:  farb and loadmap.
                     54: The program farb produces output that depends on the
                     55: time of day.  The output of loadmap depends on the
                     56: details of local software. Other than that, the results should
                     57: be the same. For example, the tests run on a PDP-11/70 under Version 7
                     58: are identical to the standard ones, except for farb and loadmap.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.