Next: The test.conf test configuration, Previous: The arte.conf framework configuration, Up: Configuration files
The suite-specific configuration file needs the following four mandatory parameters:
[module].name
(Mandatory)’[module].start
(Mandatory)’none
. Also, you can use the reserved %BIN%
word
in this field to indicate the suite-specific ‘bin’ directory
(prefix/suites/[module]/bin/)
[module].stop
(Mandatory)’none
. Also, you can use the reserved %BIN%
word
in this field to indicate the suite-specific ‘bin’ directory
(prefix/suites/[module]/bin/)
[module].runtype
(Mandatory)’always
,
manual
and once
(they are explained in the next section).
In addition to the previous mandatory parameters, you can specify an unlimited number of global variables which will be available in each test of this suite:
[module].[VARNAME]
(Optional)’start
/stop
commands with
the reserved %BIN%
word, you can specify in any of these environment
variables the %COMMON%
reserved word to indicate the suite-specific
‘common’ directory (prefix/suites/[module]/common/). You must take
into account that the test-specific configuration may override the value of any
environment variable defined in the suite-specific configuration.
An example of [module].conf configuration file is the following, the configuration file for the ‘generic’ module (named generic.conf).
# generic.conf # Configuration file for the GENERIC suite in the ARTE testing framework # Configuration parameters (mandatory) generic.name="This is the GENERIC module, dude" generic.start="%BIN%/start_generic.sh" generic.stop="%BIN%/start_generic.sh" # Available runtypes (mandatory): always | manual | once generic.runtype="always" # Environment vars for the TCL interpreter (optional) generic.HELLO="Hello World" generic.INPUTFILE="%COMMON%/inputfile.txt" |