Objects that we are unable to identify.

Ask general questions here.
Santhosh
Posts: 33
Joined: Fri Aug 10, 2018 5:51 am

Objects that we are unable to identify.

Post by Santhosh » Thu Aug 23, 2018 3:50 pm

Hi,
Ranorex is identifies the window, while comes to particular elements in the same window its difficult to identify. Sometimes it is identifying the drop down element only and other elements its not identifying..

Here is a below environment details:

Ranorex Version - Ranorex 8.
Windows Version - Windows 10
.Net Version - .Net Framework 4.5.2
Application - Desktop based
Application built - Powerbuilder

Please help me out on the same.

Regards,
Santosh

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

Re: Objects that we are unable to identify.

Post by odklizec » Thu Aug 23, 2018 5:42 pm

Hi,

I’m afraid, without, at very least, Ranorex snapshot, it’s very hard to suggest something reliable or even provide sensible suggestion what’s wrong and what to do.

If possible create a Ranorex snapshot (not screenshot) of the app/problematic controls and publish it here. Also, which Ranorex version exactly do you use? Most recent version is 8.2.1. If you are using something older, please upgrade it with actual version.

At next, if Ranorex spy recognises individual GUI elements and then the test fails to recognise them, we need exact error message you are getting (ideally, post entire report) and an example of failing xpath (as stored in repository).

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

Santhosh
Posts: 33
Joined: Fri Aug 10, 2018 5:51 am

Re: Objects that we are unable to identify.

Post by Santhosh » Fri Aug 24, 2018 5:49 am

Thanks for you reply,,

Ranorex version is 8.2.0 and we tried to identify by using Ranorex spy tool also, but not able to identify..

Please find the screenshot of the window:
Dropdown list.jpg
Hope the above information may helpful to you.

Regards,
Santosh
You do not have the required permissions to view the files attached to this post.

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

Re: Objects that we are unable to identify.

Post by odklizec » Fri Aug 24, 2018 6:31 am

Hi,

Unfortunately, what you have posted is not a snapshot but screenshot. What we need to see is the Ranorex snapshot. Please learn how to create one here...
https://www.ranorex.com/help/latest/ran ... hot-files/

You may need to use Instant Tracking to be able to catch the combo box content...
https://www.ranorex.com/help/latest/ran ... -tracking/

Current Ranorex version is 8.2.1. It may not help with your problem, but it’s worth a try and it’s always better to stay up-to-date ;)
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

Santhosh
Posts: 33
Joined: Fri Aug 10, 2018 5:51 am

Re: Objects that we are unable to identify.

Post by Santhosh » Fri Aug 24, 2018 7:29 am

Hello,,

What I am trying to explain is that, in above screenshot Ranorex is identifying the parent element like ("whole container") while comes to the children like ("Cartaira, Resindencil, Commercial, Fax, Page, E-mail, -etc") in that container its not identifying the elements. and if we click on the drop down it is identifying the element.
It is only identifying dropdowns but not other elements.

Please help me...

Regards,
Santosh

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

Re: Objects that we are unable to identify.

Post by odklizec » Fri Aug 24, 2018 7:41 am

Hi,

Yes, I understand. But as mentioned, without (at very least) snapshot, there is not much anyone here can do or suggest. Anyway, I guess that in this particular case, there is not much anyone here (including Ranorex support) can do without access to your app. So, I would suggest to create a support ticket (here) and request a remote session with Ranorex support folks.

The only thing I can suggest is to try the GDI Capture feature, which may help with identifying individual texts in your app and so you may be able to interact with controls via their labels. But this option is far from ideal and definitely not usable for complex GUI elements (like grids). But it's worth a try. You may learn about it here: https://www.ranorex.com/help/latest/ran ... e-feature/

BTW, check also this post regarding Ranorex and Powerbuilder.
viewtopic.php?f=16&t=11780&p=47351#p47351
The idea about trying to track the elements with MS Inspect tool is good one! If the MS Inspect is not able to track the elements (the same as Ranorex Spy), there is most probably a problem with MSAA implementation in your app. In other words, there is nothing Ranorex can do about it and your app must be improved if you want to automate it. But as mentioned, there may be still a chance to use the GDI Capture approach. It's just not as reliable as MSAA and much harder to use with complex elements.
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

Santhosh
Posts: 33
Joined: Fri Aug 10, 2018 5:51 am

Re: Objects that we are unable to identify.

Post by Santhosh » Fri Aug 24, 2018 10:28 am

Thanks for you suggestion,,

Attached snapshots for the tracked issues including dropdown list and item selection.
However in both the snapshots only the parent window is tracked and unable to identify the child objects.

Please see the below Ranorex Snapshots:
Item_selection.rxsnp
Dropdown.rxsnp
Regards,
Santhosh.
You do not have the required permissions to view the files attached to this post.

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

Re: Objects that we are unable to identify.

Post by odklizec » Fri Aug 24, 2018 10:35 am

Hi,

Thaks for the snapshot. As you mentioned, there is not much to see in it ;) Have you tried the MS Inspect tool?
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