verifyVisible
This is a pre-built Action located under the @Custom Element. The functionality of this Action in Avo Assure is to verify whether the specified object is visible on the web page. The result is stored in the given dynamic variable for further use during test execution.
The verifyVisible action works only when the VerifyExists action is executed in a preceding step.
Syntax
Input Value: <ObjectType>;<VisibleText(optional)>;<Index>;<abs(optional)>
<ObjectType> (Required)
Provide the object type which you want to check for visibility in the application.
<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.
<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 Visibility of a Confirmation Popup
In this example, we are explaining how to verify whether a confirmation popup is visible on the web page.
Action: verifyVisible
Input Value: button;;0
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.
Output Value: {Status}
The result of the visibility verification operation is stored in the {Status} dynamic variable, with the following possible values:
True: If the popup is visible on the screen.
False: If the popup is not visible on the screen.
Logical Explanation: The verifyVisible action reads the identification details from the Input Value column (button;;0). The action locates the specified object based on the object type and index and checks whether the popup is visible on the application interface. The execution result of the visibility verification action (True) is stored in the {Status} variable.
Example 2: Verifying Visibility of a Confirmation Popup using Optional Parameters
In this example, we are explaining how to verify whether a confirmation popup is visible on the web page using optional identification parameters.
Action: verifyVisible
Input Value: button;Next;0
The first argument (button) specifies the object type to be identified.
The second argument (Next) specifies the visible text of the object.
The third argument (0) specifies the index of the object when multiple matching elements are present.
Output Value: {Status}
The result of the visibility verification operation is stored in the {Status} dynamic variable, with the following possible values:
True: If the popup is visible on the screen.
False: If the popup is not visible on the screen.
Logical Explanation: The verifyVisible action reads the identification details from the Input Value column (button;Next;0). The action locates the specified object based on the object type, visible text, and index and checks whether the popup is visible on the application interface. The execution result of the visibility verification action is stored in the {Status} variable.
Note: Element highlighting is now available for verifyVisible action. When the Highlight check is set to Yes, the element highlighting is visible; when set to No, the element highlighting is not visible, providing better control during execution and debugging.
Last updated