> 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/dropdown/verifycount.md).

# verifyCount

This is a pre-built Action located under the captured dropdown element. The functionality of this action in Avo Assure is to verify whether the count of items provided in the input field matches the total number of options available in the dropdown. The result is stored in the given dynamic variable for further use during test execution.

## **Syntax**

**Input Value**: `<Input value>`

| Argument                            | Description                                                                                                 |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| <p>\<Input value><br>(Required)</p> | Provide the numerical value which you want to use as the expected count to verify against the actual count. |

**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: Verifying the Number of Items in a Dropdown**

In this example, we explain how to validate whether the number of items present in a dropdown matches the expected count.

* **Action**: verifyCount
* **Input Value**: 4
  * The first argument (**4**) specifies the expected number of options that should be present in the captured dropdown element.
* **Output Value**: **{Status}**
  * The verification result is stored in the **{Status}** dynamic variable with the following possible values:
    * **True**: If the dropdown item count matches the expected value.
    * **False**: If the dropdown item count does not match the expected.
* **Logical Explanation**: The **verifyCount** action reads the expected count from the **Input Value** column (**4**). The action retrieves all available options from the dropdown element and calculates the total number of items. The action compares the actual count with the expected value provided. The result of the validation (**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%2FVM178FqM428ROQFM8sE0%2Fimage.png?alt=media&amp;token=ed9e92bc-2ddb-46f9-a6a4-6ed9365ec075" 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/dropdown/verifycount.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.