mirror of
https://git.openafs.org/openafs.git
synced 2025-01-18 23:10:58 +00:00
c877c0b419
Instead of bundling our own copies of Russ's C TAP Harness, start using
source pulled from his git repository using the src/external import
mechanism. Note that we are not currently building the floating
point (is_double) portion of the harness.
In the process of doing so, we also upgrade our test harness to the latest
upstream version, 1.11. This is somewhat problematic, as there have been
some significant code changes since the version bundled with OpenAFS.
Work around these by
*) Referencing the basic.h header as <tests/tap/basic.h>, rather than
just <tap/basic.h>, to match the new upstream layout
*) Changing the include path so that the tests/ directory can be
found within it.
Change-Id: I63efbb30248165e5729005b0a791e7eb7afb051d
Reviewed-on: http://gerrit.openafs.org/7374
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Russ Allbery <rra@stanford.edu>
Reviewed-by: Derrick Brashear <shadow@dementix.org>
38 lines
1.9 KiB
Plaintext
38 lines
1.9 KiB
Plaintext
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
|
|
|