automake: DejaGnu Tests

1 
1 15.5 DejaGnu Tests
1 ==================
1 
1 If ‘dejagnu’ (https://ftp.gnu.org/gnu/dejagnu/) appears in
1 ‘AUTOMAKE_OPTIONS’, then a ‘dejagnu’-based test suite is assumed.  The
1 variable ‘DEJATOOL’ is a list of names that are passed, one at a time,
1 as the ‘--tool’ argument to ‘runtest’ invocations; it defaults to the
1 name of the package.
1 
1    The variable ‘RUNTESTDEFAULTFLAGS’ holds the ‘--tool’ and ‘--srcdir’
1 flags that are passed to dejagnu by default; this can be overridden if
1 necessary.
1 
1    The variables ‘EXPECT’ and ‘RUNTEST’ can also be overridden to
1 provide project-specific values.  For instance, you will need to do this
1 if you are testing a compiler toolchain, because the default values do
1 not take into account host and target names.
1 
1    The contents of the variable ‘RUNTESTFLAGS’ are passed to the
11 ‘runtest’ invocation.  This is considered a “user variable” (⇒User
 Variables).  If you need to set ‘runtest’ flags in ‘Makefile.am’, you
1 can use ‘AM_RUNTESTFLAGS’ instead.
1 
1    Automake will generate rules to create a local ‘site.exp’ file,
1 defining various variables detected by ‘configure’.  This file is
1 automatically read by DejaGnu.  It is OK for the user of a package to
1 edit this file in order to tune the test suite.  However this is not the
1 place where the test suite author should define new variables: this
1 should be done elsewhere in the real test suite code.  Especially,
1 ‘site.exp’ should not be distributed.
1 
1    Still, if the package author has legitimate reasons to extend
1 ‘site.exp’ at ‘make’ time, he can do so by defining the variable
1 ‘EXTRA_DEJAGNU_SITE_CONFIG’; the files listed there will be considered
1 ‘site.exp’ prerequisites, and their content will be appended to it (in
1 the same order in which they appear in ‘EXTRA_DEJAGNU_SITE_CONFIG’).
1 Note that files are _not_ distributed by default.
1 
11    For more information regarding DejaGnu test suites, see ⇒
 (dejagnu)Top.
1