> 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/grid/verify-attribute.md).

# Verify Attribute

This is a pre-built Action located under the captured **Grid Element**. The functionality of this Action in Avo Assure is to verify whether the specified attribute of the captured grid matches the expected attribute value provided in the input and store the verification result in a dynamic variable.

## Syntax

**Input Value**: `<Attribute Name>;<Attribute Value>(Optional);<css>(Optional)`

{% hint style="info" %}
**Note**:

* The Attribute Name is mandatory for this Action.
* **Attribute Value** is optional. If provided, Avo Assure verifies whether the actual attribute value matches the expected value.
* The css parameter is optional and can be used to specify that the attribute verification should be performed using CSS properties.
* Ensure that the specified attribute exists for the captured grid.
  {% endhint %}

| Argument                                  | Description                                                                                |
| ----------------------------------------- | ------------------------------------------------------------------------------------------ |
| <p>\<Attribute Name></p><p>(Required)</p> | Provide the name of the attribute to verify. For example, disabled, readonly, class or id. |
| <p>\<Attribute Value><br>(Optional)</p>   | Provide the expected value of the specified attribute.                                     |
| <p>\<css><br>(Optional)</p>               | Not Applicable                                                                             |

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

|                                |                                                                                                                |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------- |
| Argument                       | Description                                                                                                    |
| \<Dynamic Variable> (Required) | Stores the verification result as True or False, indicating whether the attribute verification was successful. |

#### Example 1: Verifying the Presence of an Attribute in a Grid

In this example, we explain how to verify whether a specific attribute is present in the captured grid.

* **Action**: VerifyAttribute
* **Input Value**: class
  * The input value (**class**) specifies the attribute name that needs to be verified in the captured grid.
* **Output Value**: {Status}
  * The verification result is stored in the **{Status}** dynamic variable.
    * **True**: If the specified attribute is present in the captured grid.
    * **False**: If the specified attribute is not present in the captured grid or the verification fails.

**Logical Explanation**: The **Verify Attribute** action takes the value from the **Input Value** column (**class**) and checks whether the specified attribute exists in the captured grid. If the attribute is found, the action stores **True** in the **{Status}** variable.

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FgqlP4VcgYhd6UEYWxvNi%2Funknown.png?alt=media&amp;token=db027031-1d44-42ed-aaa5-daac4cbab45c" alt="" height="47" width="615">

#### **Example 2: Verifying an Attribute with an Expected Value**

In this example, we explain how to verify whether a specific attribute of the captured grid matches the expected value.

* **Action**: Verify Attribute
* **Input Value**: class;ag-root ag-unselectable ag-layout-normal ag-body-horizontal-content-no-gap ag-body-vertical-content-no-gap
  * The first argument (**class**) specifies the name of the attribute to verify.
  * The second argument (**ag-root ag-unselectable ag-layout-normal ag-body-horizontal-content-no-gap ag-body-vertical-content-no-gap**) specifies the expected value of the **class** attribute.
* **Output Value:** {Status}
  * The execution result is stored in the **{Status}** dynamic variable with the following possible values:
    * **True**: If the actual value of the **class** attribute matches the expected value.
    * **False**: If the actual value does not match the expected value or the attribute is not found.
* **Logical Explanation**: The **Verify Attribute** action takes the values from the **Input Value** column (**class;ag-root ag-unselectable ag-layout-normal ag-body-horizontal-content-no-gap ag-body-vertical-content-no-gap**). The action retrieves the actual value of the specified **class** attribute from the captured grid and compares it with the expected value. If both values match, the action stores **True** in the **{Status}** variable.

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F0NIxOStW5W98XLihfNt0%2Funknown.png?alt=media&amp;token=a73cf26a-e6c4-4508-9a03-86b741ef14a9" alt="" height="45" width="626">


---

# 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/grid/verify-attribute.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.