openafs/tests
Michael Meffie d72df5a18e cmd: exit status zero from -help
Return of an exit status of zero when running commands with -help,
instead of returning an error. By general convention, and in
previous versions, tools do not not treat -help as an error.

The AFS::Command perl modules, use -help as an introspection
technique, and fail when commands run with the -help option returns
non-zero.

Change-Id: I6ecd95f6ccd07218a2657dbb4dbf1c13599159f4
Reviewed-on: http://gerrit.openafs.org/8087
Reviewed-by: Derrick Brashear <shadow@your-file-system.com>
Reviewed-by: Simon Wilkinson <simonxwilkinson@gmail.com>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
2012-09-11 11:38:57 -07:00
..
auth util: Convert to using libtool 2012-09-08 20:27:51 -07:00
bozo Introduce TAP tests of man pages for command_subcommand 2011-06-28 12:52:28 -07:00
bucoord Introduce TAP tests of man pages for command_subcommand 2011-06-28 12:52:28 -07:00
cmd cmd: exit status zero from -help 2012-09-11 11:38:57 -07:00
common tests: Abstract out code for a test RPC service 2012-06-27 07:27:42 -07:00
kauth Introduce TAP tests of man pages for command_subcommand 2011-06-28 12:52:28 -07:00
opr tests: deal with one more unsigned warning 2012-09-06 21:31:56 -07:00
ptserver Introduce TAP tests of man pages for command_subcommand 2011-06-28 12:52:28 -07:00
rpctestlib util: Convert to using libtool 2012-09-08 20:27:51 -07:00
rx rx: Build libtool library 2012-09-08 20:28:32 -07:00
tap tests: Start using the upstream C TAP harness 2012-05-11 16:36:44 -07:00
tests-lib/perl5 Introduce TAP tests of man pages for command_subcommand 2011-06-28 12:52:28 -07:00
util tests: Start using the upstream C TAP harness 2012-05-11 16:36:44 -07:00
venus Introduce TAP tests of man pages for command_subcommand 2011-06-28 12:52:28 -07:00
volser util: Convert to using libtool 2012-09-08 20:27:51 -07:00
.gitignore Import C TAP Harness 1.2 as a testing harness 2010-05-29 21:48:19 -07:00
libwrap TESTS: Add the libwrap script to "make check" to handle library paths 2012-04-16 06:02:53 -07:00
Makefile.in tests: Start using the upstream C TAP harness 2012-05-11 16:36:44 -07:00
README tests: Start using the upstream C TAP harness 2012-05-11 16:36:44 -07:00
TESTS opr: Add UUID handling functions 2012-08-14 12:53:08 -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 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.

The files comprising the test harness are sourced from the C TAP Harness 
distribution using the src/external mechanism. The upstream site for that
distribution is 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 tests/tap directory rather than modifying files
in src/external.

More information can be found in the HOWTO contained in
src/external/c-tap-harness/HOWTO