Index of /geminiatari/FILES/GNU/TESTS

 Name                    Last modified       Size  Description

 Parent Directory        24-Sep-2006 15:38      -  
 ANSIDECL.H              29-Jul-1993 02:58     3k  
 MAKEFILE.HP             29-Jul-1993 02:58     1k  
 MAKEFILE.SUN            29-Jul-1993 02:58     1k  
 MAKEFILE.TOS            29-Jul-1993 02:58     1k  
 PATCHLEV.H              29-Jul-1993 02:58     1k  
 STRERROR.C              29-Jul-1993 02:58     1k  
 TATOF.C                 29-Jul-1993 02:58     2k  
 TBCOPY.C                29-Jul-1993 02:58     3k  
 TBCOPY.OUT              29-Jul-1993 02:58     1k  
 TCTYPE.C                29-Jul-1993 02:58     2k  
 TCTYPE.OUT              29-Jul-1993 02:58    16k  
 TESTS05/                24-Sep-2006 15:36      -  
 TPRINTF.C               29-Jul-1993 02:58     4k  
 TPRINTF.OUT             29-Jul-1993 02:58     2k  
 TQSORT.C                29-Jul-1993 02:58     3k  
 TRANDM.C                29-Jul-1993 02:58     1k  
 TRDWR.C                 29-Jul-1993 02:58     3k  
 TREGEX.C                29-Jul-1993 02:58     9k  
 TSCANF.C                29-Jul-1993 02:58     3k  
 TSCANF.IN               29-Jul-1993 02:58     1k  
 TSETJM.C                29-Jul-1993 02:58     1k  
 TSIGNL.C                29-Jul-1993 02:58     1k  
 TSTDIO.C                29-Jul-1993 02:58    18k  
 TSTRING.C               29-Jul-1993 02:58    20k  
 TSTRL1.C                29-Jul-1993 02:58     3k  
 TSTRL2.C                29-Jul-1993 02:58     3k  
 TTIME.C                 29-Jul-1993 02:58     3k  

Here are a basic set of confidence tests for the C library: a lot of
work is needed to build up this set of tests and i seek your active
participation and contributions. The principles i've tried to follow
are:
	- the tests should be simple. larger tests go into the sub-dir
	big/. Performance type tests can go into perf/. The tests mostly
	test functionality. Of course this is not enough, and we should
	have performance tests alongside the functional tests, to flag
	when we break things big time performance wise (both in time and
	space). We also need to develope coverage tests.

	- the tests should be self contained: you should not have to examine
	the output, or diff the output against some file to figure out
	if the output is indeed correct, the test should check its own 
	result.

	- tests should only print out stuff when something goes wrong,
	otherwise remain silent. Of course this is not always possible
	(or followed, see tstdio for example). in such cases a .out file
        exists for you to diff against.

	- all tests should return a valid status.

	- all the tests should be 16/32 bit integer clean.

	- a test should test a small number of related functionality. that
	way its easier to isolate stuff when things go wrong.

naming:
	tests are named as  tXXXXX.c, any input files for the test
	are named tXXXXX.in, and the executables are named tXXXXXX16.ttp
	and tXXXXX32.ttp for 16/32 bit ints respectively.

cheers,
--
bang:   uunet!cadence!bammi			jwahar r. bammi
domain: bammi@cadence.com
GEnie:	J.Bammi
CIS:    71515,155