Ranorex Forum

I'm remotely connecting to a 'Windows Server 2008 R2 Standard' machine running Ranorex 4.0.2.21666. I have a series of test cases for an application running on the same machine. The test cases consist mostly of recording modules. Each individual test case usually runs fine, but it has a random chance of failing. When running all the test cases it's basically certain that some of the cases fail. This is obviously not good.

After some testing it seems that some of the clicks Ranorex are doing aren't registering. I've discerned no pattern as to which clicks that fail. Ranorex reports the clicks as happening, showing no error messages for the missed clicks themselves.

What I've tried:
Upping the duration of every action to 1000 ms.
Running without the debugger.

This hasn't helped and I've at my wit's end at this point. Any help would be appreciated.

Edit: Also, the machine in question is a virtual machine, that might apparently be important...

Hi Jocke,

First of all I would highly recommend updating Ranorex to a newer version since we have already released a bunch of bug fixes and newer versions.

If the problem still occurs within a newer version, you can try to separate the mouse click action into two separate actions as shown in the following screenshot *The additional Delay action is an optional action, but I'd recommend using it since you are working on a virtual machine.

Please also find additional information and guidelines about working remotely in our User Guide

Please let me know if this solves your issue.
Regards,
Markus (S)

Thank you for your reply.

Is this a known issue in older versions that has since been fixed? Because I understand that upgrading is quite expensive, and we're not likely to do that if the issue might not even be resolved.

Is separating the move and click actions something that can be done automatically in the recorder in our or newer versions? Doing it manually is not really feasable.

Regarding the remote testing guidelines:

• Do not Automate via Remote Desktop Window: We're not.
• Do not Close or Minimize the RDP Window: We're not.
• Disable Mouse/Keyboard Activities: Would this be likely to change anything? It's a virtual machine with only one user logged in.
• Use same Color and Resolution Settings: Irrelevant, it's the same machine.
• Increase Timeouts on Virtual Machines: Timeout are already 30 s. Also it's not a timeout problem, everything indicates the elements are properly found, they're just not clicked on properly.

Hi Jocke,

Thank you for your feedback.

We had some issues in older versions which were related to the asynchronous dispatching setting. Therefore, may I ask you to try disabling this setting as shown below? If the problem still occurs, I would recommend trying a newer version in trial mode. This allows you to evaluate the version over a period of 30 days.

Thank you for your understanding.
Regards,
Markus (S)

A combination of disabling mouse/keyboard entries during tests and disabling asynchronous dispatching seems to have resolved the issue. Thank you very much.