freebsd-dev

History

David E. O'Brien 65c045e964 Repo copy libpthreads to libkse. This introduces the WITHOUT_LIBKSE nob, and changes WITHOUT_LIBPTHREADS to mean with neither threading libs. Approved by: re(kensmith)		2007-10-09 13:42:34 +00:00
..
guard_b.c	o Include <string.h>	2005-11-19 04:45:15 +00:00
guard_b.exp	Repo copy libpthreads to libkse.	2007-10-09 13:42:34 +00:00
guard_s.pl
hello_b.c
hello_d.c
hello_d.exp	Repo copy libpthreads to libkse.	2007-10-09 13:42:34 +00:00
hello_s.c
join_leak_d.c
join_leak_d.exp	Repo copy libpthreads to libkse.	2007-10-09 13:42:34 +00:00
Makefile	libkse was renamed to libpthread.	2004-02-05 02:55:20 +00:00
mutex_d.c	o Include <sys/time.h>	2005-11-19 04:47:06 +00:00
mutex_d.exp	Repo copy libpthreads to libkse.	2007-10-09 13:42:34 +00:00
propagate_s.pl
README
sem_d.c
sem_d.exp	Repo copy libpthreads to libkse.	2007-10-09 13:42:34 +00:00
sigsuspend_d.c	Fix typo: s/_LIBC_R/_LIBC_R_/	2005-11-19 04:43:29 +00:00
sigsuspend_d.exp	Repo copy libpthreads to libkse.	2007-10-09 13:42:34 +00:00
sigwait_d.c
sigwait_d.exp	Repo copy libpthreads to libkse.	2007-10-09 13:42:34 +00:00
verify

README

$FreeBSD$

This test suite is meant to test general functionality of pthreads, as well as
provide a simple framework for regression tests.  In general, this test suite
can be used with any pthreads library, but in reality there are a number of
libpthread-specific aspects to this test suite which would require some
effort to get around if testing another pthreads library.

This test suite assumes that libpthread is installed.

There are two forms of test that the 'verify' script understands.  The simpler
form is the diff format, where the output of the test program is diff'ed with
the correspondingly named .exp file.  If there is diff output, the test fails.
The sequence test format is somewhat more complex, and is documented in the
command line usage output for verify.  The advantage of this format is that it
allows multiple tests to pass/fail within one program.

There is no driving need for test naming consistency, but the existing tests
generally follow these conventions:

<name>_d.c <name>_d.exp     : Diff mode C test and expected output file.
<name>_s.c                  : Sequence mode C test.
<name>_b*.c                 : Back end C program used by perl tests.
<name>_d.pl <name>_d.pl.exp : Diff mode perl test and expected output file.
<name>_s.pl                 : Sequence mode perl test.

<name> is something descriptive, such as "pr14685" in the case of a PR-related
regression test, or "mutex" in the case of a test of mutexes.