Ranorex Exe taking more time to find an UI Element

Technology specific object identification, supported applications, web technologies, and 3rd party controls.
Posts: 1
Joined: Thu Jul 29, 2021 8:12 am

Ranorex Exe taking more time to find an UI Element

Post by prasannak1996 » Thu Jul 29, 2021 8:27 am

We are using Ranorex to verify automation IDs of a WPF application running on a Windows Tablet (Windows 10 Enterprise LTSC). We have built Ranorex Exes and they are placed in the Tablet. Whenever I want to verify an ID, I will call the Exe using the command prompt. The Exe executes, searches for the ID, and returns results. Once the Exe is launched it is taking more than 1 minute to find the element. Sometimes, it takes even more than 2 minutes. Is this time anyway related to the Tablet's memory and performance? Any settings we need to change to make the Exe work faster?

User avatar
Ranorex Guru
Ranorex Guru
Posts: 7469
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Ranorex Exe taking more time to find an UI Element

Post by odklizec » Fri Jul 30, 2021 1:33 pm


Of course, a PC performance could play a significant role in element search speed. However, a most probable reason of slow element speed search is inefficient xpath. Could you please share a Ranorex snapshot (NOT screenshot) of typically slow to find element, including the xpath you are using in repo? Thanks.
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration