Very long delay before click

[Scary Hallo]

Hello,

I‘m a beginner in Ranorex. In a recording to automate my AUT, my problem is that I have a very long delay before a mouse click ( ca 30 seconds). It is after I rightclick on an item to open a context menu and before I leftclick to select a menu item.

There is a waning with the following text:

Item 'ParaWriteRepository.ApplicationUnderTest.Eigenschaften' could be found using its absolute path, but not using its relative path from the cached element of parent folder 'ParaWriteRepository.ApplicationUnderTest'. This can happen if either the item search timeout is too small or if items within a rooted folder do not share a common parent element. To fix this problem, first increase the item search timeout. If this does not help, create a separate rooted folder for this item or disable caching for the specified folder.

My System:
Windows 10 pro 64
AUT: Qt-Desktop-App created with VS2017 (32 bit)
Ranorex 9.0.0 (runs as administrator)

[odklizec]

Hi,

At first, your Ranorex version is quite a bit outdated and I'm afraid, also somewhat buggy. You should update to most recent 9.2 (or at very least 9.1.2).

At next, could you please upload a Ranorex snapshot (NOT screenshot) of the AUT and mainly, the problematic context menu. Plus post also the full xpath of repo element, you are using in your test. Thanks.

[Scary Hallo]

Hello,

here the snapshot of my AUT. The X-Path of that item is

Code: Select all

/form[@processname='DS6AD']//menuitem[@name='Eigenschaften']

I think the warning says, that it hat something to do with the xpath. It is not easy to track a contextmenu element from spy.

Thanks in advance

[odklizec]

Hi,

You can track context menu, using Instant Tracking feature, as described here:
https://www.ranorex.com/help/latest/ran ... -tracking/

Another possibility is to start standard tracking in Spy, press and hold F12 (this will pause tracking), do whatever you want with mouse and then, once the context menu is available, move mouse above the context menu and release F12 key to resume tracking.

BTW, the snapshot complains about QT instrumentation error:

QT_instrumentation.png

You should follow the steps from the link in error and don't forget to use most recent Ranorex version. Using 9.0.0 is just a waste of time and energy

[Scary Hallo]

I set the 'Qt-legacy automation mode' to true, to eliminate the warning.
Also I updated to Version 9.2.
Still the same delay.
I have also still problems with tracking the context-menuelement, even with Instant Tracking or with F12. I always get the parent element (container) not the menuelement.

[odklizec]

Hi,

Just take the snapshot of menu parent container. It should contain also individual menu elements?

BTW, have you tried to disable repo element Caching? Just follow the steps from error message you got.

[Scary Hallo]

OK, disabling repo element caching helped.
Don't know why but thank you for your help.

[dmconsulting1]

I have this same issue.

I created a rooted folder and moved the item there, that didn't work
I disabled cashing, but now it doesn't find anything in the parent object
I extended the timeout, but now it just takes longer to time out.

For now I have shortened the timeout so it will timeout fast. It finds the object and clicks without issue, it just looks for it forever before it does.

[odklizec]

Hi,

Have you tried to add the application process name to the Ranorex white list? Whitelisting often helps with element search times.

Also, some elements (e.g. system dialogs), with too generic xpaths, may take somewhat long to find. Unfortunately, without seeing the xpath and, at very least, Ranorex snapshot (NOT screenshot) of the problematic element, it's impossible to suggest something reliable.