mirrors/emacs
1
Fork 0
mirror of git://git.sv.gnu.org/emacs.git synced 2026-04-27 08:43:40 -07:00
Code Issues Projects Releases Wiki Activity

-> harness version 2.7

Browse source 
Copied from Perforce
 Change: 20761
 ServerID: perforce.ravenbrook.com
This commit is contained in:
Richard Tucker 1999-05-04 15:27:58 +01:00
parent 7b8fc049b7
commit 1e3b74ce7e
3 changed files with 30 additions and 44 deletions
Download patch file Download diff file Expand all files Collapse all files

11
mps/qa/test/script/help/clib
View file

@ -1,11 +1,16 @@
compile test libraries
% $HopeName: MMQA_harness!script:help:clib(trunk.3) $
% $HopeName: MMQA_harness!script:help:clib(trunk.4) $
Usage: qa clib [<options>]
'clib' recompiles the test libraries (as listed in testlib:manifest)
You must run clib before running tests with 'run', and you are
advised to run it when switching from one memory manager to another.
This should be done before running tests with 'run'. The harness
will check whether the test libraries are up-to-date when running
tests, and give an error if not.
Compiled libraries are placed in the obj:<platform>: directory.
In addition to compiling the libraries, 'clib' looks at the mps header
files and the specified link objects, to determine what mps interfaces
are available. This information is recorded in the file 'mmqasym.h'.

53
mps/qa/test/script/help/options
View file

@ -1,5 +1,5 @@
display options and their current values
% $HopeName: MMQA_harness!script:help:options(trunk.5) $
% $HopeName: MMQA_harness!script:help:options(trunk.6) $
Usage: qa options [<options>]
@ -21,48 +21,18 @@ What the options mean:
MMQA_MPS_INCLUDE_DIR / -i
a directory where the MM header files may be found. No default.
Note: if you change this setting, it may be necessary to recompile
the test libraries (qa clib).
MMQA_MPS_LINK_OBJ / -l
the MM libraries and plinth to link with. Separate multiple files
with spaces. No default.
Note: if you change this setting, it may be necessary to recompile
the test libraries (qa clib), because if may change the value of
MMQA_MPS_PRODUCT.
with spaces. (Spaces in the paths will make the test harness go
wrong, unfortunately.) No default.
MMQA_MPS_PRODUCT / -prod
Should be "epcore" or "dylan", according to which memory manager
you are testing. The only difference this makes is whether the
test harness uses the trampoline or not. Usually you will not need
to set this option, as if it is left unset, the harness will use
MPS version identification to choose the right value.
Note: if you change this setting, it may be necessary to recompile
the test libraries (qa clib).
MMQA_MPS_INTERFACE_VERSION / -v
It should be one of the following:
OS (oldstyle) release.dylan.incr.patch.11
MO (modern) release.mps.thursdaypm
GR (grotesque) release.dylan.honeybee ("space"->"arena")
BQ (baroque) release.dylan.meadowlark (needs mpsw3.h)
HU (humanist) release.dylan.kinglet (spare committed fund)
These are in order from oldest to newest, so e.g. GR is appropriate
for releases from honeybee upto but not including meadowlark. If
you just want to test a build from the trunk or a development
branch then it's anybody's guess what version you should use, if
indeed there is an appropriate one. This situation won't improve
until the MPS has an interface-version-interface -- then it can
all be automated.
The default is the most recent version. New interface versions
are added (by rit) when he discovers that the MM interface has changed
so as to require them.
If you change this setting, it is necessary to recompile the
test libraries (qa clib).
You won't normally need to (and shouldn't) set this option, which
will default to "epcore" or "dylan", whichever is appropriate to
the memory manager specified in MMQA_MPS_LINK_OBJ. If however you
want to test a memory manager which predates MPS version
identification, then you must set it manually.
MMQA_LOG_DIR / -g
the directory in which log files should be saved. Default is
@ -119,6 +89,13 @@ MMQA_DEBUG_INFO / -[no]debug
various diagnostic messages, which may or may not be useful in
the event of a problem with the test system. Not recommended.
MMQA_DANGEROUS / -[no]danger
default is 'off'. With default setting, the harness will refuse
to run a test if it believes the test libraries may not be compatible
with the current settings. Normally you will want to "qa clib" when
this happens, but to force the harness to run the test with the
old libraries (and symbol lists), turn this option on.
MMQA_MAIL_RESULTS / -[no]mail
If MAIL_RESULTS is on, then MAIL_SUBJECT will be put at the beginning
of the subject header when test logs are mailed out. Default is

10
mps/qa/test/script/help/run
View file

@ -1,10 +1,14 @@
run tests, reporting results and verdict
% $HopeName: MMQA_harness!script:help:run(trunk.2) $
% $HopeName: MMQA_harness!script:help:run(trunk.3) $
Usage: qa run [<options>] <testfile> [<testfile> ...]
'run' runs tests individually. The test libraries must previously
have been compiled with 'clib'.
'run' runs tests individually. The test libraries should previously
have been compiled with 'clib'; if the harness believes the test
libraries may not be up-to-date, it will give an error and ask
you to run 'clib' first. (You can force the harness to run a test
with potentially out-of-date libraries by specifying the "-danger"
option to 'run'. This is not recommended.)
'run' shows the test's output as it runs, then when it finishes,
displays test information, results, and the verdict: PASS or FAIL.