openafs/tests
Simon Wilkinson 3a1e129b76 tests: Add a RX functionality test
Use the rxperf performance testing tools to add a couple of simple
RX tests. The first moves 1Mbyte of data backwards and forwards 30
times. The second starts 30 threads, which each move 1MByte of data
once.

This is by no means an exhaustive test of RX, but the single and
multi-threaded invocations should provide a useful smoke test if
things get very broken.

Change-Id: I11267be067cf6c05a20aeb90a18ed4031502a1b1
Reviewed-on: http://gerrit.openafs.org/7244
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Derrick Brashear <shadow@dementix.org>
2012-04-19 05:07:19 -07:00
..
auth tests: Explicitly include DES in superuser test 2012-04-18 20:26:45 -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 tests: Add opr to the command test libraries 2012-03-24 06:19:48 -07:00
common auth: local realms configuration 2012-04-16 10:31:04 -07:00
kauth Introduce TAP tests of man pages for command_subcommand 2011-06-28 12:52:28 -07:00
opr Update .gitignore files 2012-04-18 20:26:54 -07:00
ptserver Introduce TAP tests of man pages for command_subcommand 2011-06-28 12:52:28 -07:00
rpctestlib rx: Make struct rx_connection private 2011-12-03 20:44:20 -08:00
rx tests: Add a RX functionality test 2012-04-19 05:07:19 -07:00
tap Resync test harness with C TAP Harness 1.7 2011-04-28 20:24:34 -07:00
tests-lib/perl5 Introduce TAP tests of man pages for command_subcommand 2011-06-28 12:52:28 -07:00
util tests: remove unused variable in tests/util/ktime-t.c 2012-04-09 16:18:24 -07:00
venus Introduce TAP tests of man pages for command_subcommand 2011-06-28 12:52:28 -07:00
volser tests: waitpid requires sys/wait.h 2012-04-08 18:24:58 -07:00
.gitignore Import C TAP Harness 1.2 as a testing harness 2010-05-29 21:48:19 -07:00
HOWTO Resync test harness with C TAP Harness 1.7 2011-04-28 20:24:34 -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: Add the libwrap script to "make check" to handle library paths 2012-04-16 06:02:53 -07:00
README Add additional documentation for the new test suite 2010-06-09 23:18:09 -07:00
runtests.c Resync test harness with C TAP Harness 1.7 2011-04-28 20:24:34 -07:00
TESTS tests: Add a RX functionality test 2012-04-19 05:07:19 -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.c 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.

runtests.c, tap/basic.c, tap/basic.h, tap/libtap.sh, and HOWTO come from
the C TAP Harness distribution 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 tap directory rather than modifying
basic.c, basic.h, or libtap.sh.