In order to use a configuration other than the default one,
specify the "config_module" entry in your config file.
What this configuration will do is of course up to the person
who wrote it, and hence in order to find this information out
for a particular application, run "texttest -a <app>
-help". This provides a means for configurations to explain
how they differ from the default one.
A configuration can both extend the range of command line
options available, and the config file entries that will be
interpreted and acted upon. Occasionally, they have defined new
sorts of files that define test cases and test suites, besides
the usual ones
. It can
then be useful to have the static GUI display them as such, so
there is a config file entry “definition_file_stems”
to allow this to be configured.
TextTest comes with 2 configurations to choose from -
"default" which should work anywhere, and
for use on UNIX with the SGE
grid engine installed.
It is also possible that configurations can add new
to the GUI (static or dynamic). It has been found
occasionally useful to allow this module to be different from
the module indicated by config_module so that configuring the
GUI can be done independently of configuring the procedure for
selecting and running tests. This is done via the config file
entry “interactive_action_module”, which will
default to the value of “config_module” if not