README
1The text below is the original README from the imported CSSC tests:
2
3
4This directory contains regression tests for the CSSC package.
5
6The environment variable "dir" selects where the programs to be tested
7are found, so if your machine has "genuine" SCCS in (say) /usr/sccs,
8you can say export dir=/usr/sccs and run these tests on the genuine
9article. This serves to test the test suite itself.
10
11Most of these tests contain no checks of the contents of stderr.
12Output to stdout is checked, as are return values. However, CSSC
13produces more warning messages than genuine SCCS and also these
14messages are in a different (more helpful?) format.
15
README_ORIGIN
1The files in this directory (except for the directory "common") are
2taken from the CSSC project. The files below this directory contain more
3that 1100 tests written by James Youngman. We thank James Youngman
4for providing this nice test case base that is also very useful for our
5official SCCS code.
6
7This code has been taken from CSSC-1.3.1, we introduced the following
8modifications:
9
10- $TESTING_CSSC was originally set to "true" for
11 CSSC and to "false" for other
12 software.
13
14 $TESTING_CSSC is now set to "true" by
15 our script "common/real-thing" for both
16 CSSC and recent generic SCCS (this
17 version of SCCS).
18
19 Run the tests with the environment
20 variable CSSC_ONLY=true to switch
21 back to the original behavior.
22
23
24- Test t5 from admin/r-option.sh tests for something to fail with
25 CSSC that is expected to work with SCCS.
26 As the CSSC maintainer James Youngman
27 now agrees that "admin -i ..." and
28 "admin -n ..." are equivalent calls,
29 The related action is no longer
30 expected to fail even with CSSC.
31
32 Test "t5" has been replaced by "t5a"
33 and "t5b" that test for the results
34 that are expected when using SCCS.
35
36- admin/y-flag.sh This script calles "test -e ..."
37 but the -e option to test(1) may not
38 be available with the Bourne Shell.
39 For this reason, we replaced "test -e"
40 by "test -r"
41
42
43- Test "fa11" from binary/auto.sh tries to grant that a file with the
44 content "x\000y\n" to cause SCCS to
45 initialize a history file that is
46 un-encoded. This is wrong. Leaving this
47 test as it has been would cause the
48 test suite to require the existence
49 of a CSSC-specific bug.
50
51 Test "fa11" has been modified to verify
52 that an encoded history file is created
53 instead.
54
55 A new test "fa12" has been introduced
56 that tests whether a fle with the
57 content "x\001y\n" will result in an
58 un-encoded history file.
59
60- binary/seeking.sh contained a direct call to:
61 if ( ${admin} -V 2>&1 ; echo umsp ) | grep CSSC >/dev/null
62 instead of testing $TESTING_CSSC
63
64 binary/seeking.sh now checks for
65 $TESTING_CSSC to allow the test to be
66 run for SCCS too.
67
68- year-2000/ext.sh This test used to check for a CSSC
69 specific 4-digit cut-off date extension
70 that is not implemented with SCCS.
71
72 This test has been enhanced by a test
73 for a SCCS specific 4-digit cut-off date
74 extension. This new test is now
75 enabled by $TESTING_REAL_SCCS, the
76 original test is run if
77 $TESTING_REAL_CSSC is set.
78
79Past 2011, we added the following modifications in August 2014:
80
81- $TESTING_SCCS_V6 This variable has been added in order
82 to deal with different behavior of
83 SCCS in case that SCCSv6 history files
84 are used.
85
86- Test c3 in admin/admin-hz.sh This test intentionally destroys the
87 SCCS checsum in line 1 of the history
88 file. The original code also destroys
89 the V6 header and results in "V3"
90 instead of "V6". The new code reverts
91 this accidental effect.
92
93- Text C2 in admin/comment.sh This tests checks the date/time format
94 in the delta table. As the SCCSv6
95 history format always uses a 4-digit
96 year format, the test needs to check
97 a different format whether in v4 or v6
98 mode.
99
100- binary/auto.sh Several tests are related to auto-uu-
101 encoding of files in case that there
102 is content that is unsupported by
103 SCCSv4. As SCCSv6 treats everything as
104 test files as long as there is no NUL
105 character present, these tests need
106 to be different for SCCSv6 history
107 files.
108
109- binary/seeking.sh This script contains more corner
110 cases for text vs. binary files that
111 behave different vor SCCS v4 and v6.
112
113- get/excl_ig_2.sh Warns on a SCCSv6 bug with delta -gsid
114 This has been removed after
115 delta -gsid was made working in
116 February 2015
117
118We added the following modifications in April 2015:
119
120- bsd-sccs/driver-basic.sh The "test -w file" calls have been
121 bsd-sccs/sf595594.sh replaced by "wtest -w file" calls.
122 bsd-sccs/delsfile.sh "wtest" is a shell funtion that
123 get/writable.sh uses ls -l | grep "^-r--r--r--" to
124 get/middle-fail.sh check. Needed as recent Haiku only
125 allows to run commands as root.
126
127
128If you are interested in the original version of the test suite below this
129directory, please have a look at the original code from CSSC written by
130James Youngman.
131
132