> 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/table/verifycelltooltip.md).

# VerifyCellToolTip

This is a pre-built Action located under the Table captured from the AUT Element, instructs the Avo Assure to verify if the tool tip text is present in the specified table cell and save the result in the dynamic variable.

{% hint style="warning" %}
**Note:** A tooltip for a table cell is a small pop-up box that appears when you hover your mouse over a cell in the table. It provides additional information or context about the data in that cell, helping users understand it better without cluttering the table.
{% endhint %}

### Syntax

**Input Value:** `<Row>;<Col>;<Value>`

| Argument                      | Description                                                   |
| ----------------------------- | ------------------------------------------------------------- |
| <p>\<Row><br>(Required)</p>   | Row number of the specified table cell                        |
| <p>\<Col><br>(Required)</p>   | Column number of the specified table cell                     |
| <p>\<Value><br>(Required)</p> | Tooltip text that needs to be verified for the specified cell |

**Output Value**

| Argument                                                    | Description                                                  |
| ----------------------------------------------------------- | ------------------------------------------------------------ |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This variable stores the result in the **True** or **False** |

**Example**

**Verifies whether the tooltip text for a specific cell in the table matches the expected value.**

The **Verify Cell ToolTip** action checks if the tooltip of the table cell (e.g., **6;2;Mobile**) contains the given value. If the tooltip text matches, the result is stored in the **{result}** variable with the following possible values:

* **True** – if the tooltip text is verified successfully
* **False** – if the tooltip text does not match or an error occurs

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FkinTADyVPFr3m1dGb8Ao%2Fimage.png?alt=media&amp;token=44915f7b-68fa-4fd9-a3db-d6cce8651795" 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/table/verifycelltooltip.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.