UI Identification problem under iOS With Ranorex agent 2.3.2

Mobile Testing, Android App Testing.
sdahiya
Posts: 3
Joined: Thu Sep 28, 2017 8:53 am

UI Identification problem under iOS With Ranorex agent 2.3.2

Post by sdahiya » Wed Oct 04, 2017 9:45 am

Hallo Team,

From new Ranorex library 2.3.2 onwards we have problem in identifying the UI elements. There are basically two major problems/changes:
1. with previous version of Ranorex library the UI component which were recognized as type "Text" are now recognized as type "Container".

Please see the difference in the following screenshots which are taken with older Libary and newer Library- scroll to right:
RanorexAgent_2.3.1_and_2.3.2IdentificationElements&Properties.png
RanorexAgent_2.3.1_and_2.3.2IdentificationElements&Properties.png (96.98 KiB) Viewed 630 times
(Left side - Ranorex Library- 2.3.1 and right side - Ranorex Library 2.3.2)


2. with previous version of Ranorex library, the UI component which was recognized as type "Text" was provided with attributes values but with the new libary version '2.3.2' and onwards the attribute values are missing. for exapmle #Caption and # LocalizationKey are missing attributes values in newer version of Ranorex Library.
Please see the difference in the following screenshots which are taken with older Libary and newer Library- scroll to right:
RanorexAgent_2.3.1_and_2.3.2_IdentificationElements&Properties1.png
RanorexAgent_2.3.1_and_2.3.2_IdentificationElements&Properties1.png (95.65 KiB) Viewed 630 times
(Left side - Ranorex Library- 2.3.1 and right side - Ranorex Library 2.3.2)


Can you please find out the cause with new library and possibly correct it otherwise we have almost every component which needs to be adjusted in our repository and it would be a big major change for us which we obiviously would like to avoid it.

Thanks & Regards

sdahiya
Posts: 3
Joined: Thu Sep 28, 2017 8:53 am

Re: UI Identification problem under iOS With Ranorex agent 2.3.2

Post by sdahiya » Fri Oct 06, 2017 10:35 am

I had also seen another issue alike the above: -- Please search with keywords in forum 'unable-to-detect-elements-in-ios-mobile-web-t11343'
as I am not able to post a URL link as a new user (Thats what I am getting error from Ranorex while adding URL- wierd!!!)
../forum/unable-to-detect-elements-in-ios-mobile-web-t11343.html
Only difference seems for me is "web broswer"!. In my case the UI identification issue appears on 'iOS' device instead of web browser

sdahiya
Posts: 3
Joined: Thu Sep 28, 2017 8:53 am

Re: UI Identification problem under iOS With Ranorex agent 2.3.2

Post by sdahiya » Mon Oct 09, 2017 4:30 pm

Hi,
A suggestion from Ranorex support team of upgrading Ranorex 7.2 and agent 2.3.3, the element under iOS10 were again identifiable :D
Another test with iOS 11 version was also *almost* successful :arrow: only a few of UI elements were not recognized. Rxpath for those unidentifiable elements need to be adjusted/updated inside the repository itself.

Thanks a lot to Ranorex Team :D :!:

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: UI Identification problem under iOS With Ranorex agent 2.3.2

Post by Support Team » Mon Oct 09, 2017 8:38 pm

Hello sdahiya,

Thank you for posting and following up on this post in the Ranorex forums.

I do encourage you to try upgrading to 2.3.3 as you stated, but this may not solve all of your issues in tests recorded prior to the updates. The change form xCode 8 to xCode 9, as well as the change from iOS 10 to 11 creates a fundamental difference in the application itself, and we ironed out a lot of issues in the new library 2.3.3 version. We continue to do so in future versions, but for now object recognition that I have tested in the 2.3.3 library appears to be recognizing objects well, however, you may have to go back and update your tests. The speed bump caused by Apple's changes is unavoidable, but there should not be any roadblocks here.

Please note that "//" (any descendants) included strategically in your RanoreXPath will likely help with changes to the application object tree in spy, as well as some other useful features of the RanoreXPath:

https://www.ranorex.com/help/latest/ranorexpath

If you do continue to have trouble recognizing objects in newly created tests, then please contacting [email protected] again, as we are very interested in whatever issues are stopping your testing. We will continue to work hard to stay ahead of the curve, and release bug fixes as quickly as we can.

Best of luck going forward, and I am sorry that some changes in the tree have caused previously recorded tests some issues, but you should find recording tests again is working well.

Thank you, sdahiya, for reporting issues, and helping us make Ranorex software better for you, and the entire community!

Sincerely,

- M. Kendall McIntosh
Automation Support Engineer
.
Image