• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..04-Apr-2018-

common/H31-Aug-2020-234153

cssctests/H04-May-2018-7,5274,211

sccstests/H04-Dec-2018-2,9882,053

MakefileH A D25-Aug-20202.7 KiB7649

READMEH A D17-Jan-20193.1 KiB9056

README

1The content of this directory (except for the content of the directory
2"cssctests") is part of the SCCS project. The content of the directory
3"cssctests" (except for the content of the directory "cssctests/common")
4has been taken from the CSSC project (from James Youngman).
5
6We use the 1188 tests in "cssctests" for basic testing of the SCCS project and
7the content from the directory "sccstests" for tests that are specific to this
8version of SCCS and for enhanced additional tests.
9
10To run the test, just type:
11
12	smake
13
14and check the output for problems that are flagged by the word FAIL or XFAIL.
15
16	Please report any problems!
17
18But note that some operating systems do not support everything.
19
20	-	HP-UX will e.g. fail on some tests with "Arg list too long".
21
22	-	AIX will fail with all dates before 1970 January 1
23		as the time functions in libc return -1 or such dates
24		and this will lead to dates like: 69/12/31 23:59:59
25
26If you run "smake", this will install a copy of the current SCCS binaries
27under /tmp/SCCSTEST. If you like to test something else, either manually
28create a related set of binaries under /tmp/SCCSTEST or check below how to
29use dir= to tell make to search the test binaries under a different directory.
30
31If you only like to run the tests imported from CSSC, run:
32
33	smake cssc-tests
34
35The CSSC tests give a fairly good basic test coverage, but as CSSC does not
36support every feature from SCCS, it may not be complete. See:
37cssctests/README_ORIGIN for some hints on how we changed the CSSC test suite.
38
39Running:
40
41	smake cssc-v6-tests
42
43will run the tests from above in SCCS v6 mode, but only in case that
44the SCCS implementation under test supports SCCS v6 history files.
45
46If you only like to run only the SCCS specific enhancement tests, run:
47
48	smake sccs-tests
49
50These tests in the directory sccstests do not do a full test (they assume
51that thebasic tests are in cssctests). The tests in sccstests check in
52addition:
53
54-	Some SCCS features not tested by the CSSC test suite
55
56-	Some corner cases that are supported by SCCS but prohibited by CSSC
57	and thus not checked by the CSSC test suite.
58
59-	A behavior supported by SCCS (e.g. permitting new flags in the SCCS
60	history file) and needed to permit future SCCS enhancements.
61
62-	Features added to SCCS by Sun (some of them are also found on HP-UX
63	and probably other CDE-co-developers) and not tested by the
64	CSSC test suite.
65
66-	Features added by the Schily SCCS enhancement project (e.g. permit
67	to switch off the "No id keywords" warnings via admin -fy) and not
68	tested by the CSSC test suite.
69
70-	Corner cases that have been made to work by this SCCS version,
71	e.g. support for the time period beyond 1969..2068.
72
73Running:
74
75	smake sccs-v6-tests
76
77will run the tests from above in SCCS v6 mode, but only in case that
78the SCCS implementation under test supports SCCS v6 history files.
79
80
81If you like to test other implementations or installations, run e.g.:
82
83	dir=/usr/ccs/bin smake
84
85to run all the tests against the SVr4 default install directory for SCCS.
86
87If you like to ruin the tests without the lengthy random diff compare tests, run:
88
89	NO_RANDOM=TRUE smake tests
90