---------------------------------------------------------------------------
			    The PLP Test Suite
---------------------------------------------------------------------------

You will need:

    a POSIX-compliant version of the Bourne shell (sh) --
	bash or ksh may also work.

    perl, version 4 or greater.

---------------------------------------------------------------------------

1.  unpack the tarfile in the PLP base directory (henceforth referred to as
    $(PLP)), so the TESTS directory is "parallel", as it were, to your
    build directory.

2.  cd to your build directory, run configure (if necessary), and
    type "make tests". If you have already made the executables in
    the non-testing mode, you should "make clean" first.

3.  Now, cut and paste the TESTDIR and PATH command lines, which should look
    something like this, into your testing window:

	TESTDIR=/home/jmason/plp-x.x/irix5/TESTS; export TESTDIR
	PATH=$TESTDIR/bin:$PATH; export PATH; cd $TESTDIR

    Note that this will put the testing "lpq", "lpr", "lpd" etc. into the
    path ahead of the currently installed versions. You could use the
    window you just built in as a testing window; it doesn't really
    matter.

4.  If you want to test the permissions and hostname resolution code, you
    should edit the Makefile and change the HOST_DOMAIN line so it matches
    your domain name. If you do not do this, some of the "testlib" tests
    may fail.

5.  In the testing window, type "make tests", and sit back and watch the
    fireworks. None of the tests should fail (unless you skipped stage 4
    above).

If a printing test fails, it'll leave its output in a file in the "failed"
subdirectory of TESTDIR. Also, a (hopefully) descriptive error message is
logged. To get more information about why a test failed, you may wish to
try running "lpd -D5", which should produce enough debug output to
illuminate the situation.

Sometimes, printing tests may fail with an error message similar to
"[too small: 0 < x]"; if this occurs on an NFS-mounted filesystem, and
does not happen on a second run, then chances are that it's a transitory
error caused by a bad NFS implementation (or a badly set-up filesystem).
I've observed this on HP/UX 9.03.

--j.

---------------------------------------------------------------------------

TROUBLESHOOTING:

    change-euid failed (fs mounted with -nosuid option?)

    If any of the executables give you this error, you should go back
    to the build area, run "touch libplp.tst.a", then re-run
    "make tests".
