Int4 Test Execution runtime variables | Int4 Suite Help Portal

Within Int4, ASTER runtime starts with additional variables predefined, representing the details of script execution context.

These variables are not constants! So they can be UNSET or their values can be changed within the program. If that will be the case, the program could stop making sense!

Name	Value	Comments
`_DESIGN_MODE_`	`_TRUE_` if script is running in the editor `_FALSE_` when the script runs during test execution	Indicates that the script is executed directly from the editor. It allows implementation of specific logic e.g. initialization of variables available only during Int4 Suite Test Run execution. Example: `PO = IF(_DESIGN_MODE_, "AFT_S4_123", GET_TC_VAR("PO")[1]["NEWVAR"]); PAYLOAD = IF(_DESIGN_MODE_, GET_TC_OUTPUTS()[1], GET_CONTEXT_PAYLOAD());`

Name

Value

Comments

_DESIGN_MODE_

_TRUE_ if script is running in the editor

_FALSE_ when the script runs during test execution

Indicates that the script is executed directly from the editor.

It allows implementation of specific logic e.g. initialization of variables available only during Int4 Suite Test Run execution.

Example:

PO = IF(_DESIGN_MODE_, 
          "AFT_S4_123",
          GET_TC_VAR("PO")[1]["NEWVAR"]);
          
PAYLOAD = IF(_DESIGN_MODE_,
            GET_TC_OUTPUTS()[1],
            GET_CONTEXT_PAYLOAD());