# verifyLinkText

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

{% hint style="info" %}
The **verifyLinkText** 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 link text operation. (e.g., hyperlink text)                                               |
| <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 link text you want to verify against the actual value                                                                                      |
| <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 Visible Text of a Hyperlink

In this example, we are explaining how to validate whether the visible text of a specified hyperlink matches the expected value on the web page.

* **Action**: verifyLinkText
* **Input Value**: link;;0;Home
  * The first argument (**link**) 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 hyperlink when multiple matching elements are present.
  * The fourth argument (**Home**) specifies the expected link text that needs to be verified.
* **Output Value**: {Status}
  * The result of the link text verification operation is stored in the **{Status}** dynamic variable.
    * **True**: If the link text is verified with the expected value.
    * **False**: If the link text is not verified with the expected value.
* **Logical Explanation**: The **verifyLinkText** action reads the identification details and expected link text from the **Input Value** column (**link;;0;Home**). The action locates the matching hyperlink based on the specified object type and index and compares the actual visible text of the link with the expected value. The execution result of the verification operation (True) is stored in the **{Status}** variable.

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

### **Example 2: Verifying the Visible Text of a Hyperlink using Optional Parameters**

In this example, we are explaining how to validate whether the visible text of a specified hyperlink matches the expected value on the web page using optional identification parameters.

* **Action**: verifyLinkText
* **Input Value**: link;Homepage;0;Home
  * The first argument (**link**) specifies the object type to be identified.
  * The second argument (**Homepage**) specifies the visible text of the hyperlink.
  * The third argument (**0**) specifies the index of the hyperlink when multiple matching elements are present.
  * The fourth argument (**Home**) specifies the expected link text that needs to be verified.
* **Output Value**: {Status}
  * The result of the link text verification operation is stored in the **{Status}** dynamic variable.
    * **True**: If the link text is verified with the expected value.
    * **False**: If the link text is not verified with the expected value.
* **Logical Explanation**: The **verifyLinkText** action reads the identification details and expected link text from the **Input Value** column (**link;Homepage;0;Home**). The action locates the matching hyperlink based on the specified object type, visible text, and index and compares the actual visible text of the link with the expected value. The execution result of the verification operation (True) is stored in the **{Status}** variable.

<figure><img src="/files/nRKMndzf1axLzxSJxgQF" 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/verifylinktext.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.