1
Fork 0
mirror of git://git.sv.gnu.org/emacs.git synced 2026-03-26 16:51:46 -07:00
emacs/mps/test
Gareth Rees 4b52294773 Specifying assertcond rather than assertline is likely to be more robust against code changes.
Copied from Perforce
 Change: 187203
 ServerID: perforce.ravenbrook.com
2014-10-10 22:55:48 +01:00
..
argerr More test maintenance: 2013-05-25 11:35:44 +01:00
conerr More test maintenance: 2013-05-25 11:35:44 +01:00
function Specifying assertcond rather than assertline is likely to be more robust against code changes. 2014-10-10 22:55:48 +01:00
misc Long delayed maintenance of test suite: 2013-05-25 10:33:30 +01:00
test Explain how to run the mmqa test suite on any unix. 2014-10-10 15:32:30 +01:00
testsets Specifying assertcond rather than assertline is likely to be more robust against code changes. 2014-10-10 22:55:48 +01:00
README It's better to run from test directory -- otherwise testsets will have to be rewritten. 2014-10-10 16:56:34 +01:00

$Id$

This is the Memory Management QA test harness. To use it you need
perl 5 (or higher). Go "perl qa help" for help, "perl qa options"
to see what version of the harness you have (or look at the
file "test/version").


Testing on unix
---------------

From the test directory::

    $ PLATFORM=lii6ll # substitute your platform
    $ CODE=../code # code directory of the branch you are testing
    $ make -C $CODE -f $PLATFORM.gmk VARIETY=cool $PLATFORM/cool/mps.o
    $ alias qa="perl test/qa -i $CODE -l $CODE/$PLATFORM/cool/mps.o"
    $ qa clib
    $ qa run function/5.c
    $ qa runset testsets/passing

Each test case is compiled in its turn to the file
``test/obj/$(uname -s)_$(uname -r)_$(uname -p)__unix/tmp_test``
so you can debug it with::

    $ lldb test/obj/$(uname -s)_$(uname -r)_$(uname -p)__unix/tmp_test

(Or ``gdb`` instead of ``lldb``.)