Ranorex Forum

When I trying to perform a click in any web button, Ranorex clicks before complete mouse move. This behavor just occurs in Amazon workspace, but in my desktop, Ranorex clicks normally.
There is any configuration in default mouse movement, like up the delay between mouse movement and mouse click?

Hi,

I've recently experienced a similar issue. What actually helped was reducing the mouse move time to 0

There are a couple of other things you could try:

1. Turn off Asynchronous mouse and keyboard

2. Add a Mouse -> Move before the Mouse -> Click in your module's action table and move the mouse to the element you want to click on.


In addition, make sure your web page is fully loaded (add " and state='complete'" to your XPath for the DOM) before you try any actions against it.

Hello!
Thanks for the answers, it help me a lot.
I made every sugestion and works for some objects, but not all.
I'm trying others configurations and if works I'll tell here.

wellingtonsantana wrote:Hello!
Thanks for the answers, it help me a lot.
I made every sugestion and works for some objects, but not all.
I'm trying others configurations and if works I'll tell here.

Recent changes to one of our vendor applications seems to be experiencing similar issues. In our case, it almost feels like the AUT is fighting with Ranorex. I've tried various combinations of ensurevisible, focus, moveto, and delay before actually performing the click.

What seems to happen is Ranorex locates the element and it bounces making the click function miss the button. I thought maybe this was ensurevisible pushing the button on screen and the AUT adjusting the page in reaction. Not using ensurevisible seemed to help on occasion, but not always and in some cases we needed to use ensurevisible because the button was below the fold.

Like I said, the only thing I've found to work consistently was using the performclick method.

Hello!
Can I assume as truth that issue will happen as well in any product similar as Amazon's workspace?

I don't think so. This kind of problem is highly variable and depends on many factors (AUT configuration, system under test configuration, Ranorex configuration, actual test configuration,...). Working with virtual machines is always tricky. Mouse movements and clicks could be either delayed or too fast You see, you have to debug the problem and try to change various settings to make it working. There is always a solution.