# verifyCount

This is a pre-built Action located under the **@Custom Element**. The functionality of this Action in Avo Assure is to verify the provided input count against the total number of options present in the dropdown or list. The result is stored in the given dynamic variable for further use during test execution.

{% hint style="info" %}
The **verifyCount** action works only when the **VerifyExists** action is executed in a preceding step.
{% endhint %}

## **Syntax**

**Input Value**: `<ObjectType>;<VisibleText(optional)>;<Index>;<count>;<abs(optional)>`&#x20;

| Argument                            | Description                                                                                                                                            |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p>\<ObjectType><br>(Required)</p>  | Provide the object type which you want to perform the verify count operation. (e.g., dropdown or list)                                                 |
| <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>\<count><br>(Required)</p>       | Provide the numerical value which you want to use as the expected count to verify against the actual count.                                            |
| <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 Count of Items in an Dropdown or List**

In this example, we are explaining how to verify whether the number of items present in a specified object matches the expected count in the dropdown or list.

* **Action**: verifyCount
* **Input Value**: select;;0;4
  * The first argument (**select**) 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 object when multiple matching elements are present.
  * The fourth argument (**4**) specifies the expected count of items that needs to be verified.
* **Output Value**: {Status}
  * The result of the count verification operation is stored in the **{Status}** dynamic variable.
    * **True**: If the actual count matches the expected value.
    * **False**: If the actual count does not match the expected value.
* **Logical Explanation**: The **verifyCount** action reads the identification details and expected count from the **Input Value** column (**select;;0;4**). The action locates the matching object based on the specified object type and index and verifies whether the number of items present in the dropdown or list matches the expected count. The execution result of the verification operation (True) is stored in the **{Status}** variable.

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

### **Example 2: Verifying the Count of Items in an Dropdown or List using Optional Parameters**

In this example, we are explaining how to verify whether the number of items present in a specified object matches the expected count in the dropdown or list.

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

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