198121Sgshapiro$FreeBSD: releng/10.2/lib/libkse/test/README 103412 2002-09-16 19:29:34Z mini $
264562Sgshapiro
364562SgshapiroThis test suite is meant to test general functionality of pthreads, as well as
464562Sgshapiroprovide a simple framework for regression tests.  In general, this test suite
564562Sgshapirocan be used with any pthreads library, but in reality there are a number of
664562Sgshapirolibpthread-specific aspects to this test suite which would require some
764562Sgshapiroeffort to get around if testing another pthreads library.
864562Sgshapiro
964562SgshapiroThis test suite assumes that libpthread is installed.
1064562Sgshapiro
1164562SgshapiroThere are two forms of test that the 'verify' script understands.  The simpler
1264562Sgshapiroform is the diff format, where the output of the test program is diff'ed with
1364562Sgshapirothe correspondingly named .exp file.  If there is diff output, the test fails.
1464562SgshapiroThe sequence test format is somewhat more complex, and is documented in the
1564562Sgshapirocommand line usage output for verify.  The advantage of this format is that it
1664562Sgshapiroallows multiple tests to pass/fail within one program.
1764562Sgshapiro
18There is no driving need for test naming consistency, but the existing tests
19generally follow these conventions:
20
21<name>_d.c <name>_d.exp     : Diff mode C test and expected output file.
22<name>_s.c                  : Sequence mode C test.
23<name>_b*.c                 : Back end C program used by perl tests.
24<name>_d.pl <name>_d.pl.exp : Diff mode perl test and expected output file.
25<name>_s.pl                 : Sequence mode perl test.
26
27<name> is something descriptive, such as "pr14685" in the case of a PR-related
28regression test, or "mutex" in the case of a test of mutexes.
29