# 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.

{% hint style="info" %}
The **verifyVisible** action works only when the **VerifyExists** action is executed in a preceding step.
{% endhint %}

## Syntax

**Input Value**: `<ObjectType>;<VisibleText(optional)>;<Index>;<abs(optional)>`&#x20;

| Argument                            | Description                                                                                                                                            |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p>\<ObjectType><br>(Required)</p>  | Provide the object type which you want to check for visibility in the application.                                                                     |
| <p>\<VisibleText><br>(Optional)</p> | Provide the visible text associated with the object.                                                                                                   |
| <p>\<Index><br>(Required)</p>       | <p>Provide the position of the object you want to identify based on its sequence in the application.<br><strong>Note</strong>: Index start from 0.</p> |
| <p>\<abs><br>(Optional)</p>         | Provide the absolute XPath of the object you want to identify for this operation.                                                                      |

{% hint style="info" %}
**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 (;).
  {% endhint %}

**Output Value**: `<Dynamic Variable>(Optional);<Dynamic Variable>(Optional)`

| Argument                                                    | Description                                                       |
| ----------------------------------------------------------- | ----------------------------------------------------------------- |
| \<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.

<figure><img src="/files/ok3tIyjhr2GifVYuaqbu" alt=""><figcaption></figcaption></figure>

### **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.

<figure><img src="/files/HaGoA6xpw3WKUVbkyYfX" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**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.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.avoautomation.com/avo-assure/actions/web/custom/verifyvisible-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.