openafs/tests
Andrew Deason 41dd504fe1 tests: Remove check/test/tests subdir targets
Since commit a62de618 (Build util tests properly with make check),
running 'make check' in tests/ also runs 'make check' in each of the
tests subdirectories, which builds the tests in that dir. (And the
same goes for 'make test' and 'make tests'.)

This does ensure that the tests are built before we run them, but it's
a bit strange to build the tests under 'make check', a target that
usually runs tests.

We do this in the top-level tests dir to make sure that the tests are
built, but this purpose is served by the existing 'make all' target.
So to reduce some duplication of logic, and reduce the number of
targets the subdirs need to implement, just have 'make check' depend
on 'make all', so we know the tests are built when we go to run them.

Change-Id: I2fcbe88daeeae94cd7ef7a4a8326c4b56fadee5a
Reviewed-on: https://gerrit.openafs.org/14636
Reviewed-by: Michael Meffie <mmeffie@sinenomine.net>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Benjamin Kaduk <kaduk@mit.edu>
2021-08-26 10:29:57 -04:00
..
auth tests: Remove check/test/tests subdir targets 2021-08-26 10:29:57 -04:00
bozo tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
bucoord tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
cmd tests: Remove check/test/tests subdir targets 2021-08-26 10:29:57 -04:00
common tests: Remove check/test/tests subdir targets 2021-08-26 10:29:57 -04:00
kauth tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
opr tests: Remove check/test/tests subdir targets 2021-08-26 10:29:57 -04:00
ptserver tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
rx tests: Remove check/test/tests subdir targets 2021-08-26 10:29:57 -04:00
tap tests: Remove check/test/tests subdir targets 2021-08-26 10:29:57 -04:00
tests-lib/perl5 tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
util tests: Remove check/test/tests subdir targets 2021-08-26 10:29:57 -04:00
venus tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
volser tests: Remove check/test/tests subdir targets 2021-08-26 10:29:57 -04:00
.gitignore tests: Add core to .gitignore in tests 2020-03-20 15:56:12 -04:00
libwrap tests: use exec to call libwrap'd executables 2016-12-16 16:25:58 -05:00
Makefile.in tests: Remove check/test/tests subdir targets 2021-08-26 10:29:57 -04:00
README correct whitespace errors in readme files 2013-01-07 07:40:46 -08:00
TESTS tests: Modernize writekeyfile.c 2020-06-19 11:48:57 -04: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