T-Plan Robot Enterprise 4.0.2 Doc Collection GUI Reference

10/06/15

T-Plan Robot Enterprise 4.0.2 Code Templates

1. Overview
2. Code Template Data Files
   
3. Code Template Wizard
4. Code Template Editor

1. Overview

1. Code template data files,
   
2. Code Template Wizard,
3. Code Template Editor.
   

2. Code Template Data Files

3. Code Template Wizard

• Click the icon to the left from an empty editor line and select the Insert a Code Template menu item.
• Right click an empty editor line and select the Insert a Code Template menu item.

1. Use the arrow keys or the mouse wheel to navigate through the list. You may also type the shortcut key or its part (such as the "ifep" one on the picture) to jump to a particular template or a category.
   
2. To insert the selected code template into the editor press Enter or click it with the mouse.
   
3. To cancel the wizard press Escape (Esc) or move the mouse pointer outside of the template window.
   

4. Code Template Editor

• Select the Edit -> Code Templates... item in the main application menu.
  
• Click the icon to the left from an empty editor line or right click the line, select  Insert a Code Template menu item and click the Edit code templates... menu item.

1. The Shortcut key is a unique template identifier. To keep the templates well organized it is recommended to set the first letter to the one typical for the selected template category. This system allows easy identification of the template in the List Mode of the Code Template Wizard.
2. The Default description will be displayed by the wizard. Keep it short.
3. The Standalone template check box controls how the template gets inserted into the editor. When the check box is on the template will be always created on a new line. When the check box is off the template will be just inserted into the current caret position. This mode is suitable for small "word" templates which are typically inserted into an already existing command and/or method call, for example a paramater value or a call of a frequently used variable.
4. The template category list allows to associate the template with a particular functional category. Each template must have at least one category. To create a new category use the button. To delete an existing custom category select the button. The default categories can not be changed or removed.
5. Inline templates (the Standalone template check box is off) may declare one or more value types they represent. For example, a code template intended to be used where a number is expected may be declared as the INT and/or FLOAT type. Templates that declare at least one value type will be shown in the custom input mode of the command/method call property window for parameters of the same type. The list of supported value types:
   
   

   Value Type	Description
   BOOLEAN	The boolean value type ('true' or 'false'). It is shown in the GUI as a check box or a radio button.
   COLOR	A color. It is shown in the GUI as a drop down with the default set of colors and a button allowing to add custom ones.
   COLOR_FROM_IMAGE	A color. It is shown in the GUI as a drop down with the default set of colors and a button allowing to add a custom color and/or select a color from the desktop screen.
   COLOR_LIST	A list of colors.
   DIRECTORY	A directory. The GUI shows this value type as an editable text field with a button allowing to select a directory from the local file system.
   FILE	A file. The GUI shows this value type as an editable text field with a button allowing to select a file from the local file system.
   FILELIST	A list of files.
   FLOAT	A floating point number. It is shown in the GUI as a number field.
   INT	An integer number. It is shown in the GUI as a number field.
   INT_DISPLAYED_AS_BOOLEAN	An integer number which is interpreted as a boolean value of "false" (the value of 0) or "true" (any other value).
   KEYSTROKE	A key stroke, for example "Ctrl+C". It is shown in the GUI as an editable text field with the record and Keyboard Tool buttons.
   PASSWORD	A password. It is shown in the GUI as a password field.
   POINT	A point (location) defined by the x and y coordinates. It is shown in the GUI as a pair of number fields together with a button allowing to select a point from the desktop screen.
   RECTANGLE	A rectangle defined by the x, y, height and width coordinates. It is shown in the GUI as a set of four number fields together with a button allowing to select a rectangle from the desktop screen.
   REGEXP	A java.util.regex.Pattern compliant regular expression. It is shown in the GUI as an editable text field with a button allowing to construct the expression from elements.
   STRING	A string. It is shown in the GUI as an editable text field or as a drop down.
   STRINGLIST	A list of strings.
   STRING_WITH_ACTION	A string. It is shown in the GUI as an editable text field together with a button allowing to implement a custom value selector.
   TEXT	A text. It is shown in the GUI as an editable text area (a field with multiple lines).
   TIME_INTERVAL	A time interval, such as "10s" (ten seconds).

6. There is a code editor for each of the supported test script formats, TPR (*.tpr) and Java (*.java). A valid template must provide code for at least one of the formats or for both.
7. The optional Custom description field allows to override the default description (2) with a format specific one. When populated the description will be shown by the Code Template Wizard opened for the associated test script format.
8. The template code should be provided without any indent (leading spaces) which will be created automatically. The code may be either static (plain text) or dynamic with parameters. The list of supported marks (parameters) follows:
   
   

   Parameter	Description
   ${dot}	Marks the position where to put the dot (caret) in the script editor after the template code is inserted. When used together with ${mark} it defines the end of text selection. To insert this mark you may optionally use the Mark caret button below the editor.
   ${mark}	Marks beginning of the text to select (highlight) in the script editor after the template code is inserted. It must be used in combination with ${dot}. To insert this mark you may optionally use the Mark selection button below the editor. Text selection may be optionally used to select a value or an expression which is expected to be rewritten right after the template insertion into the test script.
   ${var<N>:name1;..;nameM} ${var<N>}	Marks a place where to create a unique variable name. The <N> expression must be the variable ordinary number starting from 1, for example var1, var2, etc. The first mark of the N-th variable must contain the colon (:) followed by the semicolon separated list of one or more preferred variable names. This mark allows the template to specify that it needs to create one or more unique variables in a way that doesn't conflict with the existing test script code. When the template is being inserted into a script the framework retrieves the list of variables it uses and populates the template with a unique variable name which is not yet used. The preferred variable names serve as a prefix and they are suffixed with an ordinary number if needed. For example consider a simple template which creates a for() statement looping from 1 to 10: for (${var1:i}=0; {${var1}}<10; ${var1}={${var1}}+1) { } If such a template is inserted into a test script which already uses the 'i' variable for another purpose the framework creates a unique variable name as 'i2' and inserts the template as follows: for (i2=0; {i2}<10; i2={i2}+1) { }