verifyElementText
This is a pre-built Action located under the @Custom Element. The functionality of this Action in Avo Assure is to verify whether the text of the specified element matches the value provided in the input. The result is stored in the given dynamic variable for further use during test execution
The verifyElementText action works only when the VerifyExists action is executed in a preceding step.
Syntax
Input Value: <ObjectType>;<VisibleText(optional)>;<Index>;<value>;<abs(optional)>
<ObjectType> (Required)
Provide the object type which you want to verify available text of the object. (e.g., text box)
<VisibleText> (Optional)
Provide the visible text associated with the object.
<Index> (Required)
Provide the position of the object you want to identify based on its sequence in the application. Note: Index start from 0.
<value> (Required)
Provide the text or string which you want to verify from the text box.
<abs> (Optional)
Provide the absolute XPath of the object you want to identify for this operation.
Note:
If the last argument abs is defined, the action executes using absolute identification based on the specified absolute XPath provided in the input.
To skip an optional input value, use an extra semicolon (;).
Output Value: <Dynamic Variable>(Optional);<Dynamic Variable>(Optional)
<Dynamic Variable>(Optional);<Dynamic Variable>(Optional)
Both dynamic variable stores the status as True or False.
Example 1: Verifying Text of a UI Element
In this example, we are explaining how to verify whether the text displayed on a specific object in the application matches the expected value.
Action: verifyElementText
Input Value: button;;0;Log In
The first argument (button) specifies the object type to be identified.
The second argument is left blank to skip an optional value.
The third argument (0) specifies the index of the object when multiple matching elements are present.
The fourth argument (Log In) specifies the expected text that needs to be verified on the object.
Output Value: {Status}
The result of the text verification operation is stored in the {Status} dynamic variable, with the following possible values:
True: If the text is matches the expected text.
False: If the text does not match.
Logical Explanation: The verifyElementText action reads the identification details and expected text from the Input Value column (button;;0;Log In). The action locates the matching UI element based on the specified object type and index, retrieves the text displayed on the element, and compares it with the provided expected value. The execution result of the verification action (True) is stored in the {Status} variable.
Example 2: Verifying Text of a UI Element using Optional Parameters
In this example, we are explaining how to verify whether the text displayed on a specific object matches the expected value using optional identification parameters.
Action: verifyElementText
Input Value: button;Log In;0;Log In
The first argument (button) specifies the object type to be identified.
The second argument (Log In) specifies the visible text of the object.
The third argument (0) specifies the index of the object when multiple matching elements are present.
The fourth argument (Log In) specifies the expected text that needs to be verified on the object.
Output Value: {Status}
The result of the text verification operation is stored in the {Status} dynamic variable, with the following possible values:
True: If the text matches the expected text.
False: If the text does not match.
Logical Explanation: The verifyElementText action reads the identification details from the Input Value column (button;Log In;0;Log In). The action locates the matching UI element using the provided object type, visible text, and index and then retrieves the displayed text, and compares it with the expected value. The execution result of the verification action (True) is stored in the {Status} variable.
Last updated