Importing Configuration files




For TETware and TET Users an import function has been provided for importing configuration values. Importing configuration is performed on a per Test Run basis. The following types of configuration file are supported for import: For each configuration file imported the file is parsed and values that TETware professional understands are placed into the configuration for the given Test Run. Values that TETware professional does not understand are added to the User defined variables for a Test Run. All lines in the configuration file that start with # are ignored as comment lines. Comment lines are not imported since it is impossible to define rules that would capture the many different ways of commenting that are possible.

User Defined Variables

Imported User defined values will be added to the table in the User Defined variables tab, for more information on User Defined Variables click here. The mode of operation that is given to the imported User defined variable is determined by the type of configuration file that is imported. For instance, if a Build mode configuration file is imported then all User Defined variables in that file will be given a mode of Build in the User defined variables table.

Distributed config files

It is also possible to import a distributed configuration file (usually called tetdist.cfg). When importing a distributed configuration file you MUST have all the remote systems that have values in the distributed configuration file already added to the Test Run. i.e. if the distributed configuration file contains a value TET_REM001_TET_ROOT then a remote system with a system number of 001 must already be present in the Test Run for that value to be imported correctly.

How to import a configuration file

To import a configuration file you can either: Regardless of the method of import, a file selection dialog is then displayed from which the User can browse the file system and choose a configuration file. A file filter of *.cfg is also given to filter for configuration files that are given the default extension of cfg.

If a Remote System is highlighted in the Test Run tree node, the above importing functions of Build mode, Execute mode, and Clean mode will be specific for that Remote System.

Important notes

Please note that the parser for the configuration files will split any valid lines (lines not blank and not beginning with #) on "=", so any malformed lines will be added without verification. It is the Users responsibility to ensure that the configuration file is correct and contains values that are valid and have meaning to TETware professional and their Test Cases.



© The Open Group 1995-2002