The LFET.Project.ini file

In order to define individual project adjustments for decision tables,

a 'Project.ini' (alternatively LFET.Project.ini)

file can also be created. If necessary, several Project.ini-files can also be nested, see: Several Project.ini files.

Project.ini files are searched for backwards in the folder structure starting from the location of the decision table. See also: Search for Project.ini files.

  • Keys that should be “global” in the project for all decision tables are defined in the Project.ini file.

  • Keys that are to apply only to one decision table (for example, optionally the name of a test-suite) are defined in the decision table with the syntax $$key-name = value. Generally, decision table prolog is used for it.

  • All keys can also be used, either in curly or square brackets, as part of the arguments on the right hand side through the ${key-name} or $[key-name] syntax.

  • Important note: For multi-level path specifications "/" must be used instead of "\" as a separator, i.e. not Java\Source but: Java/Source

  • For relative paths, the location of the Project.ini file is used as the basis for forming the absolute path.

If required, you can also define your own keys in the decision tables themselves both in the 'Project.ini' file and using the syntax $$key = value. The definition of own keys in decision tables is created in the same way as the definition of language-related generation parameters.

Key definitions in decision tables overwrite same name definitions from the “Project.ini“ file.

If an undefined key, e.g. ${not.present} is used as an argument, this expression remains unchanged. In a follow-up processing, the existence or non-existence of individual keys can be easily recognized and it can be decided whether e.g. for a decision table a test suite exists and whether it should be started or not.

Contents of this chapter