41.12

Variables

The following options pertain to variable binding.

3.0+When binding variables, expand values immediately (System)

Server script name: OPT_VARIABLE_IMMEDIATE_BINDING

When a set of variable bindings is pushed onto a variable stack, any additional variable references in the values of these variables can either be expanded immediately, or the values can be left unchanged to be expanded lazily as needed. This is explained in detail in section 6.9.

For immediate expansion turn this option on, for lazy expansion turn it off.

3.0+Fall back to lazy binding if immediate binding fails (System)

Server script name: OPT_VARIABLE_LAZY_FALLBACK

Old tests that rely on lazy variable binding may fail with the new default of immediate binding. If this option is activated, variables that cannot be bound immediately due to references to not-yet-defined variables are bound lazily instead and a warning is issued. To get rid of the warning simply change the value of the respective variable to use explicit lazy binding with '$_'. Please see section 6.9 for further information.

5.1+Enable 'Local variable' attribute by default (System)

Server script name: OPT_VARIABLE_LAZY_FALLBACK

Many nodes have a 'Local variable' attribute that determines whether a result variable should get stored locally or as a global variable. If this option is activated, newly created nodes of that kind will have the 'Local variable' attribute set. Get more information about local and global variables in Variable levels.

9.0+Warn, if directly expanded variables in script expressions contain escape characters (System)

Server script name: OPT_WARN_FOR_ESCAPE_CHARS_IN_EXPANSIONS_FOR_SCRIPTS

It is possible to use variable expansions of the form $(name) or ${group:name} for Script expressions. In some cases the variable value contains unintentionally certain escape characters: If, for example, the variable path has the value C:\Users\test\new (instead of C:\\Users\\test\\new) and is used in a script like "$(path)"=="", the sequences \U, \t, and \n will be interpreted as escape characters, which can lead to surprising errors. If this option is active, QF-Test will log a warning in such cases. To avoid such problems, use rc.getStr in scripts (see subsection 11.3.3.1 for details).

Furthermore, various kinds of variables can be defined here. These are explained in chapter 6.