README revision 16
116SalmThe files in this directory with suffixes `.t', `.d', `.r' and `.err' are 216Salmused for testing ed. To run the tests, set the ED variable in the Makefile 316Salmfor the path name of the program to be tested (e.g., /bin/ed), and type 416Salm`make'. The tests do not exhaustively verify POSIX compliance nor do 516Salmthey verify correct 8-bit or long line support. 616Salm 716SalmThe test file suffixes have the following meanings: 816Salm.t Template - a list of ed commands from which an ed script is 916Salm constructed 1016Salm.d Data - read by an ed script 1116Salm.r Result - the expected output after processing data via an ed 1216Salm script. 1316Salm.err Error - invalid ed commands that should generate an error 1416Salm 1516SalmThe output of the tests is written to the two files err.o and scripts.o. 1616SalmAt the end of the tests, these files are grep'ed for error messages, 1716Salmwhich look like: 1816Salm *** The script u.ed exited abnormally *** 1916Salmor: 2016Salm *** Output u.o of script u.ed is incorrect *** 2116Salm 2216SalmIt is assumed that the ed being tested processes escapes (\) in file names. 2316SalmThis is so that a name starting with bang (!) can be read, via: 2416Salm r \!file 2516SalmWithout the escape, a POSIX ed would attempt to read the output of 2616Salmthe shell command `file'. If the ed being tested does not support escape 2716Salmprocessing on file names, then the script `mkscripts.sh' should be modified 2816Salmaccordingly. 2916Salm 3016SalmThe POSIX requirement that an address range not be used where at most 3116Salma single address is expected has been relaxed in this version of ed. 3216SalmTherefore, the following scripts which test for compliance with this 3316SalmPOSIX rule exit abnormally: 3416Salm=-err.ed 3516Salma1-err.ed 3616Salmi1-err.ed 3716Salmk1-err.ed 3816Salmr1-err.ed 3916Salm 4016SalmIn addition, one of !1-err.ed or !2.ed will fail, depending on whether or 4116Salmnot ed was compiled with the VI_BANG directive. 42