159612Sjasone$FreeBSD$ 259612Sjasone 359612SjasoneThis test suite is meant to test general functionality of pthreads, as well as 459612Sjasoneprovide a simple framework for regression tests. In general, this test suite 559612Sjasonecan be used with any pthreads library, but in reality there are a number of 6103412Sminilibpthread-specific aspects to this test suite which would require some 7103412Sminieffort to get around if testing another pthreads library. 859612Sjasone 9103412SminiThis test suite assumes that libpthread is installed. 1059612Sjasone 1159612SjasoneThere are two forms of test that the 'verify' script understands. The simpler 1259612Sjasoneform is the diff format, where the output of the test program is diff'ed with 1359612Sjasonethe correspondingly named .exp file. If there is diff output, the test fails. 1459612SjasoneThe sequence test format is somewhat more complex, and is documented in the 1559612Sjasonecommand line usage output for verify. The advantage of this format is that it 1659612Sjasoneallows multiple tests to pass/fail within one program. 1759612Sjasone 1859612SjasoneThere is no driving need for test naming consistency, but the existing tests 1959612Sjasonegenerally follow these conventions: 2059612Sjasone 2159612Sjasone<name>_d.c <name>_d.exp : Diff mode C test and expected output file. 2259612Sjasone<name>_s.c : Sequence mode C test. 2359612Sjasone<name>_b*.c : Back end C program used by perl tests. 2459612Sjasone<name>_d.pl <name>_d.pl.exp : Diff mode perl test and expected output file. 2559612Sjasone<name>_s.pl : Sequence mode perl test. 2659612Sjasone 2759612Sjasone<name> is something descriptive, such as "pr14685" in the case of a PR-related 2859612Sjasoneregression test, or "mutex" in the case of a test of mutexes. 29