File: README

package info (click to toggle)
tla 1.3.5%2Bdfsg1-2
  • links: PTS
  • area: main
  • in suites: bullseye, buster, stretch
  • size: 22,292 kB
  • ctags: 11,952
  • sloc: ansic: 149,771; sh: 16,009; xml: 2,689; lisp: 1,927; makefile: 1,064; cpp: 363; tcl: 230; awk: 48; sed: 25
file content (71 lines) | stat: -rw-r--r-- 2,056 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71

                       Bob's changeset Test Rig


These are (one version of) the scripts we've been using to do
"burn-in" testing on the changeset/do-changeset tools and larch's
mkpatch/dopatch.

They are not yet integrated into the configure/build system of
this package -- you have to run them by hand.

Briefly, these perform end-to-end checks on the changeset tools as
follows:

a) generate an ORIG tree with some random elements

b) copy ORIG to make a MOD tree.  perform a randomly selected
   bunch of edits on this tree (add and delete files, directories, and
   symlinks, change file contents, rename things, etc.).

c) generate a changeset from ORIG to MOD

d) copy ORIG to make TARGET

e) apply the changeset to TARGET

f) compare MOD and TARGET

g) assign ORIG = NEW-ORIG

h) goto step (b)

There are various parameters you can tweak in the source code (e.g.,
changing the relatively likelihood of various edit operations).   As
well, you test changeset/do-changeset or mkpatch/dopatch or
mkpatch/do-changeset or changeset/do-patch.

WARNING: skim the code a bit first.   There is a hard-wired path
in run-tests.sh script -- the script will create files under that
directory AND `rm -rf' files under that directory: so read first and
run with caution.

Thanks to Robert Anderson for writing this suite and spending a number
of long nights on IRC as he sent me failed test cases (often carefully
minimized by hand) and I pushed back fixes to my archive mirror.



                           WHAT YOU CAN DO

*) Play with the parameters and do some long test runs.

*) Look for ways to verify and/or improve test case coverage.

*) Work on making it portable among posix shells (e.g., don't rely
   on $RANDOM)

*) Generalize the tests to test other tagging methods.

*) Derive some new tests from this to test the archive transaction
   commands: imprev, cmtrev, tagrev, and getrev.

*) Generalize the tests to test auto-changelogs

*) Other clever and helpful things :-)


# tag: Tom Lord Sat Jun  7 11:30:20 2003 (changeset-tests/README)
#