openafs/tests
Marc Dionne 12e2d47a1c tests: Improve afstest_UnlinkTestConfig cleanup
Make afstest_UnlinkTestConfig clean up and remove the specified
directory regardless of which files are present.  This means
the function no longer has to track the current state of which
files may be present as tests are added and modified.

A sanity check is added to prevent damage in case the function is
called for an inappropriate directory.

As before, no cleaning is done if the test is run outside of a
"make check".

Change-Id: Idd092040496aaa2566c8693496fefd7d6f247565
Reviewed-on: http://gerrit.openafs.org/9703
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Jeffrey Altman <jaltman@your-file-system.com>
Reviewed-by: Derrick Brashear <shadow@your-file-system.com>
2013-05-28 15:57:31 -07:00
..
auth tests: Improve failure mode for unresolvable hostname 2013-02-17 20:51:15 -08:00
bozo tests: make a plan for man page checks 2013-05-01 07:19:01 -07:00
bucoord tests: make a plan for man page checks 2013-05-01 07:19:01 -07:00
cmd cmd: exit status zero from -help 2012-09-11 11:38:57 -07:00
common tests: Improve afstest_UnlinkTestConfig cleanup 2013-05-28 15:57:31 -07:00
kauth tests: make a plan for man page checks 2013-05-01 07:19:01 -07:00
opr opr: Don't confuse isLast and isEnd 2012-11-23 06:18:31 -08:00
ptserver tests: make a plan for man page checks 2013-05-01 07:19:01 -07:00
rpctestlib util: Convert to using libtool 2012-09-08 20:27:51 -07:00
rx tests: posix signal constants in rx/perf test 2013-05-01 07:18:19 -07:00
tap tests: Start using the upstream C TAP harness 2012-05-11 16:36:44 -07:00
tests-lib/perl5 tests: make a plan for man page checks 2013-05-01 07:19:01 -07:00
util tests: Start using the upstream C TAP harness 2012-05-11 16:36:44 -07:00
venus tests: make a plan for man page checks 2013-05-01 07:19:01 -07:00
volser tests: make a plan for man page checks 2013-05-01 07:19:01 -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: Fix fallout from cleanup change 2012-11-01 10:51:53 -07:00
README correct whitespace errors in readme files 2013-01-07 07:40:46 -08:00
TESTS opr: Add dictionary implementation 2012-11-01 12:18:01 -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