> 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/element/verifyelementtext.md).

# verifyElementText

This is a pre-built Action located under the captured element. The functionality of this Action in Avo Assure is to verify whether the given input text matches the text of the specified captured element. The 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 against the captured element content. |

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

| Argument                                                    | Description                                                       |
| ----------------------------------------------------------- | ----------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This dynamic variable stores the status as **True** or **False**. |

### **Example: Validating the Text of a UI Element**

In this example, we explain how to validate whether the text of a captured UI element matches the expected value.

* **Action**: verifyElementText
* **Input Value**: Drag me
  * The value (**Drag me**) specifies the expected text that the action will compare with the actual text of the captured element.
* **Output Value**: {Status}
  * The result of the verification is stored in this **{Status}** dynamic variable with the following possible values:
    * **True**: If the element’s text matches the expected value.
    * **False**: If the element’s text is not matches the expected value.
* **Logical Explanation**: The **verifyElementText** action takes the value from the **Input Value** column (**Drag me**) and compares it with the actual visible text of the targeted element in the application. The result of this operation (**True**) is stored in the **{Status}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FpRRD35sZw7VXKLjDbCWa%2Fimage.png?alt=media&amp;token=80150b4b-fde3-4de9-8d66-2898a48c58bd" 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/element/verifyelementtext.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.