Logical and Looping Operations

Keyword: IF

Description: This keyword or action instructs Avo Assure Client to check if the condition is true or false.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

(<operand1>;<operator>; <operand2>)

Text
Static values/ Dynamic variables
Supported operators: >, <, ==, >=, <=, != along with the logical operators AND, OR, NOT

Note:

The “if” keyword should be mandatorily succeeded by the “endIf” keyword and can contain multiple elseIf’s and else in that order.
The expression should be closed within parenthesis (), and at least 2 operands and 1 operator should be present.
To compare empty strings or whitespaces, it has to be passed through the dynamic variable.
Special characters should be passed through dynamic variables.
No “(&)” i.e. parenthesis are allowed in naming dynamic variable.
Operands AND, OP, NOT must be capitalized.
Users can use “if” and “endIf” in different testcase within the same scenario.

The snippet of the keyword is mentioned in the “else” keyword.

Keyword: ELSE

Description: This keyword or action instructs Avo Assure Client to execute the statements between the keywords “else” and “endIf”.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

Else

Note: The “else” keyword should be mandatorily preceded by the “if” keyword and succeeded by the “endIf” keyword.

Find the snippet of the keyword below:

In the above example, after the test case debug, it checks the condition, and if it is false, it executes the statements between keywords “else” and “endIf”.

Keyword: ELSEIF

Description: This keyword or action instructs Avo Assure Client to check if the condition is true or false after an original condition is verified and failed by the “if” keyword.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

elseIf

(<operand1>;

<operator>; <operand2>)

Text
Static values/ Dynamic variables
Supported operators: >, <, ==, >=, <=, != along with the logical operators AND, OR, NOT

Note: The “elseIf” keyword should be mandatorily preceded by the “if” keyword and succeeded by another “elseIf” or “else” or “endIf” keyword.

Find the snippet of the keyword below:

In the above example, after the test case debug, it checks if the condition is true/false after an original condition is verified and failed by the “if” keyword.

Keyword: ENDIF

Description: This keyword or action instructs Avo Assure Client to execute the steps within the “if” and “endIf” keywords.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

endIf

Note: The “endIf” keyword should be mandatorily preceded by “if”/”if-elseIf”/”if-else” keyword combinations.

The snippet of the keyword is mentioned in “elseIf” keyword.

Keyword: FOR

Description: This keyword or action instructs Avo Assure Client to execute the steps within the “for” and “endFor” keywords for the specified number of times or count.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

for

Text
Static values/ Dynamic variables

Note: The “for” keyword should be mandatorily succeeded by the “endFor” keyword (after the steps).

Find the snippet of the keyword below:

In the above example, after the test case debug, it executes the steps with the “for” and “endFor” for 2 times.

Keyword: ENDFOR

Description: This keyword or action instructs Avo Assure Client to execute the steps within the “for” and “endFor” keywords for the specified number of times or count.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

endFor

Note: The “endIf” keyword should be mandatorily preceded by the “for” keyword.

The snippet of the keyword is mentioned in the “for” keyword.

Keyword: GETPARAM

Description: This keyword or action instructs Avo Assure Client to execute the steps within the “StartLoop” and “EndLoop” of getParam.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getParam

<file path>; <sheetname in case of excel> (Mandatory) <row count> OR <start row- end row> as third input

Text
Static values/ Dynamic variables
Supported File Types: .xml, .xls, .xlsx, .csv and Avo Assure data tables

Note:

The user is advised to specify the number of rows in a range to be executed in the getParam, else the iterations may run for the maximum number of rows in that worksheet, irrespective of the reference column.
The user can give a range as follows: D:\sample.xlsx;Sheet;2-4 (The first row of the Excel sheet is considered as a header.)
If the user wants to execute a single row, then input is given as below: D:\sample.xlsx;Sheet1;3
Input format for .csv file, for example: D:\sample.csv
Input format for .xml file, for example: D:\sample.XML
The input format for Avo Assure data table, for example, avoassure/DataTableName
If there are any duplicate column names in the non-reference columns, the user will get the duplicate columns exist error message, and getParam will not work.

Find the snippet of the keyword below while using an XML file for data parameterization:

In the above example, after the test case debug, it takes the input from the specified XML file. It executes the setTagValue keyword (with the input containing the value of the key/tag named “ZIP” in the XML file) within the “StartLoop” and “EndLoop” of “getParam”.

Find the snippet of the keyword below while using an Excel file for data parameterization:

In the above example, after the test case debug, it takes the input from the “Sheet1” of “sample” Excel and executes the found keyword within the “StartLoop” and “EndLoop” of getParam”.

Find the snippet of the keyword below while using an Assure data table for data parameterization:

In the above example, after the test case debug, it takes the input from the SampleDataTable and executes the displayVariableValue keyword within the “StartLoop” and “EndLoop” of getParam”.