Object identification takes a long time-nearly a minute

Technology specific object identification, supported applications, web technologies, and 3rd party controls.
occ1
Posts: 1
Joined: Thu Jul 30, 2015 9:26 am

Object identification takes a long time-nearly a minute

Post by occ1 » Thu Jul 30, 2015 9:35 am

Hi,

We downloaded a trial version of Ranorex(5.3) and tested it against our huge desktop application. Our company has a huge desktop application with SQL Server as back end. We started recording scripts and Ranorex identified objects in the login window quickly. But moving onto other windows of our application which had a lot of tabs and lot of objects, Ranorex became slow while recording and playing back. We found out that Ranorex was taking a long time(nearly a minute) to search for the object in the window that contained lot of tabs and objects.

We have also tried enabling the 32/64 bit bridge in the automation settings. But performance was the same.

Could someone help us on this? We are not able to proceed further with testing the trial version without this getting solved.

Thanks!

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

Re: Object identification takes a long time-nearly a minute

Post by odklizec » Fri Jul 31, 2015 7:04 am

Hi,

At first, try the latest version 5.4 instead of the old and no longer supported 5.3. If it's 5.3.0, there were some critical bugs affecting the runtime performance. So you should either to use 5.3.3 (last supported 5.3 version) or better latest 5.4.

Next, please let us know some more details about your system (physical or virtual machine, version of OS, how much RAM, etc...).

Also, it would be really helpful if you post the Ranorex snapshot of your application under test. Learn how to create one here:
http://www.ranorex.com/support/user-gui ... files.html

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