> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/web/textbox/verifytext.md).

# verifyText

This is a pre-built Action located under the captured textbox element. The functionality of this Action in Avo Assure is to verify whether the text present in the textbox matches the input value specified in the **Input Value** column. The verification result is stored in a dynamic variable for further use during test execution.

## **Syntax**

**Input Value**: `<input value>`

| Argument                            | Description                                          |
| ----------------------------------- | ---------------------------------------------------- |
| <p>\<input value><br>(Required)</p> | Provide the text to verify with the textbox content. |

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

{% hint style="info" %}
**Note:** The **Verify Text** action supports only editable textboxes. It does not support read-only textboxes.
{% endhint %}

#### Example: Verifying the Value of a Textbox

In this example, we explain how to verify whether the text present in a textbox matches a specified input value using the **verifyText** action.

* **Action**: verifyText
* **Input Value**: Home Page
  * The input value (**Home Page**) specifies the text to be compared with the existing content of the textbox during execution.
* **Output Value**: {Status}
  * The result of the verifying text operation is stored in the **{Status}** dynamic variable, which returns one of the following values:
    * **True**: If the current text matches the specified input value.
    * **False**: If the current text not matches the specified input value.
* **Logical Explanation**: The **verifyText** action takes the value from the **Input Value** column (**Home Page**) and compares it with the text currently present in the targeted textbox. The result of this comparison is stored in the **{Status}** variable as true.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F0EURirwI2F37Ep9XD8db%2Fimage.png?alt=media&amp;token=3018d92a-cb06-40c8-91cc-06cb4d7f8d46" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/actions/web/textbox/verifytext.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.