openafs/tests
Andrew Deason 6f5f13795a tests: Check for vlserver startup
Currently, afstest_StartVLServer waits for a fixed amount of time (5
seconds) for the vlserver to startup. This means each test that runs a
vlserver takes at least 5 seconds, which adds up very quickly when new
tests are added for vlserver functionality.

Instead of waiting 5 seconds each time, change afstest_StartVLServer
to check if the vlserver has started up, and to wait a much shorter
time if it hasn't finished starting up yet. Specifically, wait until
the "Starting AFS vlserver" message appears in VLLog, and the
UBIK_RECHAVEDB recovery state bit is set. This allows vlserver-based
tests to run much more quickly.

Change-Id: I74015670a301980e6d89b3149ed9f2a6c1a40523
Reviewed-on: https://gerrit.openafs.org/14804
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Cheyenne Wills <cwills@sinenomine.net>
Reviewed-by: Benjamin Kaduk <kaduk@mit.edu>
2021-10-27 01:07:05 -04:00
..
auth tests: Introduce afstest.pm 2021-10-03 17:55:18 -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: Check for vlserver startup 2021-10-27 01:07:05 -04:00
kauth tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
opr tests: Introduce afstest.pm 2021-10-03 17:55:18 -04:00
ptserver tests: Add existing-database test for pt_util 2021-10-08 00:05:02 -04:00
rx tests: Introduce afstest.pm 2021-10-03 17:55:18 -04:00
tap tests: Remove check/test/tests subdir targets 2021-08-26 10:29:57 -04:00
tests-lib/perl5 tests: Introduce afstest.pm 2021-10-03 17:55:18 -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