# verifyButtonName

This is a pre-built Action located under the **@Custom Element**. The functionality of this Action in Avo Assure is to check the name present on the button specified in the input value. The result is stored in the given dynamic variable for further use during test execution.

{% hint style="info" %}
The **verifyButtonName** 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 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>\<value><br>(Required)</p>       | Provide the expected value which you want to verify.                                                                                                   |
| <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) | This dynamic variable stores the result of the verification as **True** or **False** |

### **Example 1: Verifying the Name of a Button**

In this example, we are explaining how to verify whether the name of a specified button matches the expected value on the application.

* **Action**: Verify Button Name
* **Input Value**: button;;0;Log In
  * 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 button when multiple matching elements are present.
  * The fourth argument (**Log In**) specifies the expected button name that needs to be verified.
* **Output Value**: {Status}
  * The result of the button name verification operation is stored in the **{Status}** dynamic variable.
    * **True**: If the button name is verified the expected value.
    * **False**: If the button name is not verified the expected value.
* **Logical Explanation**: The **verifyButtonName** action reads the identification details and expected button name from the **Input Value** column (**button;;0;Log In**). The action locates the matching button based on the specified object type and index and verifies whether the actual button name matches the expected value. The execution result of the verification operation (True) is stored in the **{Status}** variable.

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

### **Example 2: Verifying the Name of a Button using Optional Parameters**

In this example, we are explaining how to verify whether the name of a specified button matches the expected value on the application using optional identification parameters.

* **Action**: Verify Button Name
* **Input Value**: button;Submit;0;Log In
  * The first argument (**button**) specifies the object type to be identified.
  * The second argument (**Submit**) specifies the visible text of the button.
  * The third argument (**0**) specifies the index of the button when multiple matching elements are present.
  * The fourth argument (**Log In**) specifies the expected button name that needs to be verified.
* **Output Value**: {Status}
  * The result of the button name verification operation is stored in the **{Status}** dynamic variable.
    * **True**: If the button name is verified the expected value.
    * **False**: If the button name is not verified the expected value.
* **Logical Explanation**: The **verifyButtonName** action reads the identification details and expected button name from the **Input Value** column (**button;Submit;0;Log In**). The action locates the matching button based on the specified object type, visible text, and index and verifies whether the actual button name matches the expected value. The execution result of the verification operation (True) is stored in the **{Status}** variable.

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