Autotest test suites support the following options:
In parallel mode, the standard input device of the testsuite script is not available to commands inside a test group. Furthermore, banner lines are not printed, and the summary line for each test group is output after the test group completes. Summary lines may appear unordered. If verbose and trace output are enabled (see below), they may appear intermixed from concurrently running tests.
Parallel mode requires the mkfifo command to work, and will be
silently disabled otherwise.
clean
Make targets.
By default all tests are performed (or described with --list) silently in the default environment, but the environment, set of tests, and verbosity level can be tuned:
The variable AUTOTEST_PATH
specifies the testing path to prepend
to PATH. Relative directory names (not starting with
‘/’) are considered to be relative to the top level of the
package being built. All directories are made absolute, first
starting from the top level build tree, then from the
source tree. For instance ‘./testsuite
AUTOTEST_PATH=tests:bin’ for a /src/foo-1.0 source package built
in /tmp/foo results in ‘/tmp/foo/tests:/tmp/foo/bin’ and
then ‘/src/foo-1.0/tests:/src/foo-1.0/bin’ being prepended to
PATH.
AT_SETUP
or AT_KEYWORDS
) that match all keywords
of the comma separated list keywords, case-insensitively. Use
‘!’ immediately before the keyword to invert the selection for this
keyword. By default, the keywords match whole words; enclose them in
‘.*’ to also match parts of words.
For example, running
./testsuite -k 'autoupdate,.*FUNC.*'
selects all tests tagged ‘autoupdate’ and with tags containing ‘FUNC’ (as in ‘AC_CHECK_FUNC’, ‘AC_FUNC_ALLOCA’, etc.), while
./testsuite -k '!autoupdate' -k '.*FUNC.*'
selects all tests not tagged ‘autoupdate’ or with tags
containing ‘FUNC’.
AT_COLOR_TESTS
is used by
the testsuite author, or the argument ‘auto’ is given, then test
results are colored if standard output is connected to a terminal.
Besides these options accepted by every Autotest testsuite, the
testsuite author might have added package-specific options
via the AT_ARG_OPTION
and AT_ARG_OPTION_ARG
macros
(see Writing Testsuites); refer to testsuite --help and
the package documentation for details.