Rdb: Ruby-Nachbau der MWC /rdb-Werkzeuge
This commit is contained in:
@@ -0,0 +1,64 @@
|
||||
.TH testall "" "" "/rdb Command"
|
||||
.PC "Test all /rdb programs in directory $RDB/demo"
|
||||
\fBtestall [ > \fItestall.new \fB]\fR
|
||||
.PP
|
||||
.II "program^test"
|
||||
The command
|
||||
.B testall
|
||||
runs most of the
|
||||
.B /rdb
|
||||
programs with the files in the
|
||||
.BR $RDB/demo .
|
||||
You should run
|
||||
.B testall
|
||||
in directory
|
||||
.BR $RDB/demo ,
|
||||
because the test files are there.
|
||||
.PP
|
||||
.B testall
|
||||
writes the output of each example to the standard output.
|
||||
We suggest that you store the output in file
|
||||
.BR $RDB/demo/testall.old .
|
||||
Thereafter, you can check if the behavior of a test program has changed,
|
||||
by using the COHERENT command
|
||||
.B diff
|
||||
to compare the output of
|
||||
.B testall
|
||||
with the contents of
|
||||
.BR $RDB/demo/testall.old .
|
||||
.B /rdb
|
||||
performs this testing when the
|
||||
.B /rdb
|
||||
database is installed on a computer, and when code is changed.
|
||||
.SH Example
|
||||
First go to the demo directory,
|
||||
assuming the path is
|
||||
.BR /usr/rdb/demo :
|
||||
.DM
|
||||
cd /usr/rdb/demo
|
||||
testall > testall.new
|
||||
diff testall.old testall.new
|
||||
.DE
|
||||
.PP
|
||||
The command
|
||||
.B diff
|
||||
finds and displays any differences between
|
||||
.B testfile.old
|
||||
and
|
||||
.BR testfile.new .
|
||||
After careful checking, if differences are correct, type:
|
||||
.DM
|
||||
mv testall.new testall.old
|
||||
.DE
|
||||
.PP
|
||||
or
|
||||
.DM
|
||||
rm testall.new
|
||||
.DE
|
||||
.PP
|
||||
This saves space, because these files are large.
|
||||
.SH "See Also"
|
||||
COHERENT Lexicon:
|
||||
.B
|
||||
diff
|
||||
.R
|
||||
Reference in New Issue
Block a user