WPF Desktop application Object Identification is slow

Technology specific object identification, supported applications, web technologies, and 3rd party controls.
Posts: 36
Joined: Thu Nov 08, 2018 2:22 am

WPF Desktop application Object Identification is slow

Post by praneet » Wed Apr 29, 2020 5:27 pm


I am working on a WPF desktop application.For tracking the element as well as for identifying the tracked element ranorex is taking more than a minute,due to which my single excel row is taking almost 5 mins to get executed which has hardly 5 columns in it.
I have added my process to Whitelist and changed WPF plugin to WPFImproved. :cry: :cry:
Can anyone please suggest any solution for fast identification of elements

Thanks in advance

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

Re: WPF Desktop application Object Identification is slow

Post by odklizec » Thu Apr 30, 2020 8:25 am


I'm afraid, this kind of issue is not something that could be solved here. Definitely not without seeing, at very least, a Ranorex snapshot of the problematic element(s) and a complete xpath that typically takes too long to find. Also, are you using most recent Ranorex 9.3.1?

If you cannot share the snapshot/xpath, try to contact Ranorex support and request a remote session, so they can analyze the problem on your machine. Seriously, there is nothing anyone here can do or suggest without seeing your environment, test suite and app under test.

BTW, I see you've asked almost identical questions in the past...
https://www.ranorex.com/forum/viewtopic ... 585#p59585
https://www.ranorex.com/forum/viewtopic ... 683#p57683
In both cases, you were using an obsolete Ranorex version and you failed to post, at very least, Ranorex snapshot of the app under test. I think your best hope is to update Ranorex and then, if problem still exists, contact Ranorex support.
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