testsuite Invocation

Go forward to Making testsuite Scripts
Go backward to Writing
Go up to Using Autotest
Go to the top op autoconf

Running `testsuite' Scripts

Autotest test suites support the following arguments:
     Display the list of options and exit successfully.
     Display the version of the test suite and exit successfully.
     Remove all the files the test suite might have created and exit.
     Meant for `clean' Makefile targets.
     List all the tests (or only the selection), including their
     possible keywords.
   By default all the tests are performed (or described with `--list')
in the default environment first silently, then verbosely, but the
environment, set of tests, and verbosity level can be tuned:
     Set the environment VARIABLE to VALUE.  Do not run `FOO=foo
     ./testsuite' as debugging scripts would then run in a different
     The variable `AUTOTEST_PATH' specifies the testing path to prepend
     to `PATH'.  It handles specially relative paths (not starting with
     `/'): they are considered to be relative to the top level of the
     package being built.  All the 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'.
     Add the corresponding test groups, with obvious semantics, to the
     Add to the selection the test groups which title or keywords
     (arguments to `AT_SETUP' or `AT_KEYWORDS') match _all_ the keywords
     of the comma separated list KEYWORDS.
     Running `./testsuite -k autoupdate,FUNC' will select all the tests
     tagged with `autoupdate' _and_ `FUNC' (as in `AC_CHECK_FUNC',
     `AC_FUNC_FNMATCH' etc.) while `./testsuite -k autoupdate -k FUNC'
     runs all the tests tagged with `autoupdate' _or_ `FUNC'.
     If any test fails, immediately abort testing.  It implies
     `--debug': post test group clean up, debugging script generation,
     and logging are inhibited.  This option is meant for the full test
     suite, it is not really useful for generated debugging scripts.
     Force more verbosity in the detailed output of what is being done.
     This is the default for debugging scripts.
     Do not remove the files after a test group was performed --but
     they are still removed _before_, therefore using this option is
     sane when running several test groups.  Do not create debugging
     scripts.  Do not log (in order to preserve supposedly existing
     full log file).  This is the default for debugging scripts, but it
     can also be useful to debug the testsuite itself.
     Trigger shell tracing of the test groups.