Ranorex Forum

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?

Hi,

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.