Ranorex Forum

I am running Ranorex 7.0.1 on Windows 10 16299.16 (Redstone 3) and I have found that every time the following code executes, the test "waits" for 3 minutes until continuing.

Host.Local.Find<Ranorex.Form>("./form/titlebar/button[@accessiblename='Close']/../../", Application.FrameworkTuning.Instance.DefaultFormSearchTimeout)

The timeout variable is set to 30 seconds.

It seems that any time I try to search for forms or form elements, I see this 3 minute wait. It doesn't appear that the 30 second timeout is being honored.

The odd part is this only happens on Windows 10 16299.16. I run the same test on any other version of Windows 10/8.1/7 and the code returns in around 30 seconds.

Has anyone seen this type of behavior?

Hi,

Please post a Ranorex snapshot (NOT screenshot) for the problematic element, ideally both on working and non-working windows version. Without, at very least, Ranorex snapshot, there is not much anyone here can do or suggest.

At next, Ranorex 7.0.1 is about 6 months old, so I would really recommended you to update it with most recent version (7.2.0). There were many fixes and enhancements done between 7.0.1 and 7.2.0 so it's a very good idea to update your old version.

Hello,

I am unable to post a snapshot of a specific element as the problem is not with one in particular.

The call is meant to find all instances of the button and return its grandparent (the form) starting from the Host element.

The number of forms at the time of the call differs for each test.

I wanted to know if anyone had encountered an issue where the timeout for the Adapter.Find method was not being honored?

Hi,

You don't have to post the snapshot of a particular element. However, you should, at least, be able to post the snapshot of result of search in spy, using the provided xpath. Have you ever tried the xpath in spy (on problematic system)?

In my opinion, the xpath is too general and so it may take very long to find particular element(s). Either this, or there is something noticeably different on mentioned OS. Hence the snapshot from multiple systems would help to analyze the problem. And of course, there is always a possibility of bug in 7.0.1, which is why I suggested updating to latest 7.2. Your version is quite old and I'm afraid, no longer supported.