Common in iOS
Keyword: VERIFYDISABLED
Description: This keyword or action instructs Avo Assure Client to verify whether the specified object is disabled in the AUT.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyDisabled | NA | (Optional) | NA |
Find the snippet of the keyword below:
For the above keyword, after the test case debug, the element will be verified on its disabled status, and the execution status “True”/ “False” will be stored in the output variable (if specified).
Keyword: VERIFYENABLED
Description: This keyword or action instructs Avo Assure Client to verify whether the specified object is enabled in the AUT.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyEnabled | NA | (Optional) | NA |
Find the snippet of the keyword below:
For the above keyword, after the test case debug, the element will be verified if it is enabled, and the execution status “True”/ “False” will be stored in the output variable (if specified).
Keyword: VERIFYDOESNOTEXISTS
Description: This keyword or action instructs Avo Assure Client to verify if the object does not exist on the web page of the AUT.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyDoesNotExists | NA | (Optional) | NA |
Find the snippet of the keyword below:
For the above keyword, after the test case debug, the element will be verified if it does not exist, and the execution status “True”/ “False” will be stored in the output variable (if specified).
Keyword: VERIFYEXISTS
Description: This keyword or action instructs Avo Assure Client to verify if the object exists in the AUT.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyExists | NA | (Optional) | NA |
Find the snippet of the keyword below:
For the above keyword, after the test case debug, the element will be verified if it exists, and the execution status “True” or “False” will be stored in the output variable (if specified).
Keyword: VERIFYHIDDEN
Description: This keyword or action instructs Avo Assure Client to verify whether the specified object is hidden. If it is hidden, it is displayed as “True”, else, it is displayed as “False”.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyHidden | NA | (Optional) | NA |
Find the snippet of the keyword below:
For the above keyword, after the test case debug, the element will be verified if it is hidden, and the execution status “True”/ “False” will be stored in the output variable (if specified).
Keyword: VERIFYVISIBLE
Description: This keyword or action instructs Avo Assure Client to verify if the object is visible.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyVisible | NA | (Optional) | NA |
Find the snippet of the keyword below:
For the above keyword, after the test case debug, the element will be verified if it is visible, and the execution status “True”/ “False” will be stored in the output variable (if specified).
Keyword: WAITFORELEMENTEXISTS
Description: This keyword or action instructs Avo Assure Client to wait for the element in AUT to exist for the time specified by the timeout property in the config file.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
waitForElementExists | NA | (Optional) | NA |
Note: “Config.json” file TimeOut value is 5 sec. (“timeOut”: “5”)
Find the snippet of the keyword below:
For the above keyword, after the test case debug, it will wait for the element in AUT to be visible for the specified ‘TimeOut’ value, and the execution status “True”/ “False” will be stored in the output variable (if specified).
Last updated