11.7 Running the GPC Test Suite
Note: If you have installed a GPC binary distribution, you
usually don't have the Test Suite installed (you can download the
GPC source distribution to get it, however), so this section does
not apply to you. Still, you can find in the section
`Contributing Tests to the Test Suite' how to report GPC bugs
in the form of new test programs so we can fix them as fast as
possible.
The files in the test directory and subdirectories are for testing
GPC only and should not be of any other use.
Note: A few of the tests do not make sense on all systems. They are
equipped with checks and will be skipped if they find the system not
suitable. Skipped tests do not indicate a GPC bug, unless
you have a reason to be sure that the particular test should make
sense on your system.
-
To run the whole Test Suite, type `make' in the test directory
(or `make check' in the `p' object directory after
building GPC).
-
The output will show all errors encountered (hopefully none) and
tests skipped, and finally display a summary giving the number of
successful, failed and skipped tests. Any failed test indicates a
bug in GPC which should be reported to the GPC mailing list,
gpc@gnu.de. Don't forget to mention the operating system
you ran the test on and any other relevant information about what
you did.
-
You can also type `make pascal.check-long' to get a long output
which is a sequence of file names followed by `OK' for
successful tests, `SKIPPED' for skipped tests (both in capital
letters), and anything else for failed tests.
-
To run only some of the tests, you can type something like
`make MASK="foo[1-7]*.pas"' or
`make MASK="foo42.pas" pascal.check-long'.
-
To clean up after running the tests, type `make clean'.
This document was generated
by Frank Heckenbach on May, 10 2002
using texi2html