Skip to main content

    Action: LoadProject

    Function: The action compiles the active application and downloads it to the controller.

    Call: Projects test driver

    Tab: Configuration

    Load project

    Path of the project file to be loaded

    Example: D:\Projects\Test.project

    Table 63. Update

    Storage format (uses current profile as storage format)

    standard icon: The project is updated to the format for the current storage profile when it loads.

    All available versions

    standard icon: The Compiler version, Library version and Visualization version are updated.

    • Compiler Version

      standard icon: The compiler version is updated.

    • Library version

      standard icon: The versions of the used libraries are updated.

    • Visualization Profile

      standard icon: The visualization profile of the project is updated.



    Table 64. Error Handling

    Fail on missing libraries

    standard icon: If a library is missing in the project, then the action fails.

    Other message boxes

    • Report as error: All other messages are displayed as errors.

    • Acknowledge: All other messages have to be acknowledged.

    • Forward (show message boxes): All other messages are only displayed.



    Table 65. Installer Integration

    Disable Project Inspection (>=SP18)

    standard icon: When loading the project, the dialog for reloading missing add-ons is disabled.



    Tab: Parameters

    The parameters defined on the Parameters tab are used to exchange values between test script variables and parameters of test actions. Parameters can be used as placeholders on the Configuration tab. For this, the name of the parameter is set in braces in the configuration dialog. Example: {name}.

    Tip

    Variables defined globally in the script (with the prefix $GLOBALS.) can be used directly in the test action. It is not necessary to use input parameters for passing. Using output parameters is necessary for writing global variables.

    Input parameters: When executing the test action, the values of the test script variables are passed to the input parameters of the test action and can be used in the configuration of the test action.

    Output parameters: When executing the test action, the values of the output parameters of the test action are passed to the test script variables and can be used (for example, in other test actions).

    Name

    Name of the input/output parameter

    This name is defined in addition to the variable name to identify the origin of the parameter when it is passed to another script. During the test run, this name is displayed as the Outer name on the Variables (scope #<n>) tab in the Test progress window.

    Background: When a script A calls another script B, and its variable x passes y as a parameter to the script B, then the parameter y is the variable y from the point of view of script B.

    To see that this variable is recognized as variable x "outside" of script B, there is the Name column ("Outer name"). The variable y has the name x in the scope pf script B because it has been passed as variable x to the parameter y in the scope of the calling script A.

    Variable

    Name of the test script variable

    Example: TS_CaseA_Result

    Move Up

    Moves the selected variable one line up

    Move Down

    Moves the selected variable one line down

    Remove

    Removes the selected variable from the list