Page 1 of 1

Not able to recognize GUi element

Posted: Mon Nov 02, 2015 2:06 pm
by kgasimov
Hi,

After upgrade to 5.4.3 I have a problem with regocnize of GUI elements. What can cause this?

Kamal

Re: Not able to recognize GUi element

Posted: Mon Nov 02, 2015 2:20 pm
by odklizec
Hi,

It's hard to say without more details about your AUT, what version of Ranorex you upgraded from, etc...

Please answer the following questions...
- what error message exactly you getting?
- tell us more about the failing GUI element (used GUI technology). Ranorex snapshot would be extremely helpful!
- xpath that worked fine in your previous Ranorex version?
- what's the xpath if you track the element with 5.4.3?

Re: Not able to recognize GUi element

Posted: Mon Nov 02, 2015 2:34 pm
by kgasimov
- The previous version was 5.2 and worked fine.
- There are not any error message.
- Header of page, manu item, button and etc
- Because I can not recognize GUI element, there are not any xpath.

Print screen sent to [email protected]

Re: Not able to recognize GUi element

Posted: Mon Nov 02, 2015 2:51 pm
by odklizec
OK, there were many breaking changes introduced between 5.2 and 5.4.3. You need to check release notes available here:
http://www.ranorex.com/free-trial/release-notes.html
There were introduced also new native plugins (WPF, JAVA SWT, and maybe some more), which replaced old plugins).

Sending screenshot will probably not help anything as the screenshot is not very useful here. What I've asked about is a Ranorex Snapshot. It's a special XML file holding the structure of GUI, which can be saved and open via Ranorex Spy. You can find more details about it here:
http://www.ranorex.com/support/user-gui ... files.html

Re: Not able to recognize GUi element

Posted: Mon Nov 02, 2015 3:02 pm
by kgasimov
Hi,

I sent snapshot of my app to support email

Re: Not able to recognize GUi element

Posted: Thu Nov 12, 2015 11:36 am
by Support Team
Hi all,

I just want to inform you that the problem was related to a corrupt installation of the .NET Framework.
We have resolved the issue by performing a clean installation of all components (.NET Framework and Software Prerequisites)

Regards,
Markus (S)