> 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/desktop/iris/common-iris-keywords/mouse-hover-iris.md).

# Mouse Hover IRIS

This is pre-built Action located under the IRIS Element. It instructs the Avo Assure Client to mouse hover on IRIS object which is captured from desktop application and save the result in output variable as ‘True’ or ‘False’.

### Syntax  

**Input:** `N/A`

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

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FiZUwbISUnhSh4Ij5qKBg%2Fimage.png?alt=media&amp;token=77a3b8cf-d0a6-4b7c-9d24-ed8e211c3929" alt=""><figcaption></figcaption></figure>

### **Usecase/Example**

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FeT8d7TzVt9Hoq6g46r0O%2Fimage.png?alt=media&amp;token=dd7a412f-224b-4ca6-a671-5a172b1ac7ae" alt=""><figcaption></figcaption></figure>

### **Scenario:** Simulate Mouse Hover to Verify Tooltip in Desktop Application.

Consider a scenario where a desktop application is being automated for testing, and a button displays a tooltip when the mouse hovers over it. The tooltip contains additional information or instructions, such as **Click here to save your progress.** With the help of the **Mouse Hover IRIS** action, the mouse hovering over the button is simulated.

### Expected Result

When the mouse hovers over the **Save** button, a tooltip should appear displaying the text **Click here to save your progress** and store the result in output variable.

### **Output**

The Mouse hover IRIS action performed, and output stored in {Status} variable as ‘True’.


---

# 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/desktop/iris/common-iris-keywords/mouse-hover-iris.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.
