# verifyText

This is a pre-built Action located under the **@Custom Element**. The functionality of this Action in Avo Assure is to verify the text in the specified textbox against the value provided in the input. The result is stored in the given dynamic variable for further use during test execution.

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

## **Syntax**

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

| Argument                            | Description                                                                                                                                            |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p>\<ObjectType><br>(Required)</p>  | Provide the object type which you want to perform the verify text operation. (e.g., text box)                                                          |
| <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>\<value><br>(Required)</p>       | Provide the text or string which you want to verify in the text box.                                                                                   |
| <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 the Presence of Text in a UI Element**

In this example, we are explaining how to verify whether a specific text is present in a defined object on the application.

* **Action**: verifyText
* **Input Value**: textbox;;1;Pass\@1999
  * The first argument (**textbox**) specifies the object type to be identified.
  * The second argument is left blank to skip an optional value.
  * The third argument (**1**) specifies the index of the object when multiple matching elements are present.
  * The fourth argument (**Pass\@1999**) specifies the text that needs to be verified in the object.
* **Output Value**: {Status}
  * The result of the text verification operation is stored in the **{Status}** dynamic variable.
    * **True**: If the specified text is present in the object.
    * **False**: If the specified text is not present in the object.
* **Logical Explanation**: The **verifyText** action reads the identification details and verification text from the **Input Value** column (**textbox;;1;Pass\@1999**). The action locates the matching object based on the specified object type and index and verifies whether the given text exists within the object. The execution result of the verification operation (True) is stored in the **{Status}** variable.

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

### **Example 2: Verifying the Presence of Text using Optional Parameters**

In this example, we are explaining how to verify whether a specific text is present in a defined object on the application using optional identification parameters.

* **Action**: verifyText
* **Input Value**: textbox;Password;1;Pass\@1999
  * The first argument (**textbox**) specifies the object type to be identified.
  * The second argument (**Password**) specifies the visible text of the object.
  * The third argument (**1**) specifies the index of the object when multiple matching elements are present.
  * The fourth argument (**Pass\@1999**) specifies the text that needs to be verified in 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 specified text is verified successfully.
    * **False**: If the specified text is not present in the object.
* **Logical Explanation**: The **verifyText** action reads the identification details and verification text from the **Input Value** column (**textbox;Password;1;Pass\@1999**). The action locates the matching object based on the specified object type, visible text, and index and checks whether the given text exists in the object. The execution result of the verification operation is stored as (True) in the **{Status}** variable.

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


---

# 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-1/verifytext.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.