(autoconf.info)testsuite Invocation

Next: Making testsuite Scripts Prev: Writing Testsuites Up: Using Autotest

18.3 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.

`-C DIR'
     Change the current directory to DIR before creating any files.
     Useful for running the testsuite in a subdirectory from a top-level

     Remove all the files the test suite might have created and exit.
     Meant for `clean' Make targets.

     List all the tests (or only the selection), including their
     possible keywords.

   By default all 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.  Use this rather than
     `FOO=foo ./testsuite' as debugging scripts would then run in a
     different environment.

     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'.

     Add the corresponding test groups, with obvious semantics, to the

     Add to the selection the test groups with title or keywords
     (arguments to `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'.

     If any test fails, immediately abort testing.  It implies
     `--debug': post test group clean up, and top-level 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.  Create debugging scripts.
     Do not overwrite the top-level 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.

automatically generated by info2www