openafs/tests
Derrick Brashear 19869b100c test suite warning safety
make test suite compile without warning

Change-Id: I4e4b63d6ce2ae73e5458913aa81308b2691044a9
Reviewed-on: http://gerrit.openafs.org/2223
Reviewed-by: Andrew Deason <adeason@sinenomine.net>
Reviewed-by: Derrick Brashear <shadow@dementia.org>
Tested-by: Derrick Brashear <shadow@dementia.org>
2010-06-22 08:47:58 -07:00
..
tap Fix the trailing #endif comment in tests/tap/basic.h 2010-06-09 10:40:29 -07:00
util test suite warning safety 2010-06-22 08:47:58 -07:00
.gitignore Import C TAP Harness 1.2 as a testing harness 2010-05-29 21:48:19 -07:00
HOWTO Add additional documentation for the new test suite 2010-06-09 23:18:09 -07:00
Makefile.in Build util tests properly with make check 2010-06-14 18:06:42 -07:00
README Add additional documentation for the new test suite 2010-06-09 23:18:09 -07:00
runtests.c test suite warning safety 2010-06-22 08:47:58 -07:00
TESTS Add a sample test program to the new test suite 2010-05-29 21:48:40 -07:00

This directory contains a test harness and the beginnings of what is
intended to become the primary OpenAFS test suite.  The tests in this
directory are run when "make check" is run at the top level of the OpenAFS
tree.

runtests.c is the test harness, and TESTS is the list of tests that it
will run.  If you add a new test, add it to TESTS as well.  All tests must
be executables (possibly shell scripts or Perl scripts) that end in either
".t" or "-t", but should be listed in TESTS without that suffix.

Tests should be organized into subdirectories, and where it makes sense to
do so, those subdirectories should match the subdirectory names under src
in the AFS source tree.  In other words, tests for src/util/* should go in
a directory named util, tests for the libkopenafs library should go in a
directory named kopenafs, and so forth.  To integrate with the build
system, each subdirectory will need to have its own Makefile.in and be
added to the list of generated Makefiles in configure.in at the top
level.   The Makefile.in in this directory will also need to be modified
to recurse into any new directories.  See util/Makefile.in for an example
of how to write a Makefile.in for a new test directory.

runtests.c, tap/basic.c, tap/basic.h, tap/libtap.sh, and HOWTO come from
the C TAP Harness distribution at:

    http://www.eyrie.org/~eagle/software/c-tap-harness/

but feel free to propose modifications directly through OpenAFS Gerrit.
Russ Allbery will take care of merging modifications upstream.  However,
OpenAFS-specific modifications should not be made to those files.  To add
additional OpenAFS-specific code to the TAP library, add additional *.c
and *.h (or *.sh) files to the tap directory rather than modifying
basic.c, basic.h, or libtap.sh.