README revision 1.3
11.2ScgdThe files in this directory with suffixes `.t', `.d', `.r' and `.err' are
21.2Scgdused for testing ed.  To run the tests, set the ED variable in the Makefile
31.2Scgdfor the path name of the program to be tested (e.g., /bin/ed), and type
41.2Scgd`make'.  The tests do not exhaustively verify POSIX compliance.
51.1Scgd
61.2ScgdThe output of the tests is written to the two files err.o and scripts.o.
71.2ScgdAt the end of the tests, these files are grep'ed for error messages,
81.2Scgdwhich look like:
91.1Scgd	*** The script u.ed exited abnormally ***
101.1Scgdor:
111.1Scgd	*** Output u.o of script u.ed is incorrect ***
121.1Scgd
131.1ScgdIt is assumed that the ed being tested processes escapes (\) in file names.
141.1ScgdThis is so that a name starting with bang (!) can be read, via:
151.1Scgd	r \!file
161.1ScgdWithout the escape, a POSIX ed would attempt to read the output of
171.2Scgdthe shell command `file'.  If the ed being tested does not support escape
181.2Scgdprocessing on file names, then the script `mkscripts.sh' should be modified
191.2Scgdaccordingly.
201.1Scgd
211.2ScgdThe POSIX requirement that an address range not be used where at most
221.2Scgda single address is expected has been relaxed in this version of ed.
231.2ScgdTherefore, the  following scripts  which test for compliance with this
241.2ScgdPOSIX rule exit abnormally:
251.2Scgd=-err.ed
261.2Scgda1-err.ed
271.2Scgdi1-err.ed
281.2Scgdk1-err.ed
291.2Scgdr1-err.ed
301.3Salm
311.3SalmIn addition, one of !1-err.ed or !2.ed will fail, depending on whether or
321.3Salmnot ed was compiled with the VI_BANG directive.
33