Hi,
We are using Ranorex 6.0.1.
We have set of scripts developed with Ranorex 6.0.1 and objects(all controls) were identified correctly in particular Draft of AUT say Draft 1.
We upgraded the application to Draft 2 and Ranorex stopped identifying one control object. That object is of Custom control type.
This same object was identified correctly in previous Draft. And we checked with AUT developers too and they had not done any change which could cause this .i.e, No change on .NET Runtime Version, No change on Target CPU, No change in Custom Control between the drafts.
We are not able to sort out the exact reason for this. So what can go wrong ?
Spy/Studio is not identifying a custom cntrl aftr AUT update
Re: Spy/Studio is not identifying a custom cntrl aftr AUT update
Hi,
Could you upload a Ranorex Snapshot and tell us, which element exactly you want to identify? (please also add screenshots) This would help us identifying the problem.
It seems like, there must have something changed in your new application.
Additionally, be aware, that you are using an old Ranorex Studio version.
It´s always a good idea to update to the latest version (6.2.1)
regards,
qwertzu
Could you upload a Ranorex Snapshot and tell us, which element exactly you want to identify? (please also add screenshots) This would help us identifying the problem.
It seems like, there must have something changed in your new application.
Additionally, be aware, that you are using an old Ranorex Studio version.
It´s always a good idea to update to the latest version (6.2.1)
regards,
qwertzu
Last edited by qwertzu on Thu Mar 23, 2017 11:19 am, edited 1 time in total.
Re: Spy/Studio is not identifying a custom cntrl aftr AUT update
Hi,
At first, Ranorex 6.0.1 is too old and no longer supported, not to mention it's (along with 6.0.0) somewhat buggy I would strongly recommend to update to latest 6.2.1 (or at very least 6.1).
Additionally, without seeing the xpath of failing element, exact error message and Ranorex snapshot (NOT screenshot) of the failing element, it's next to impossible to tell what's wrong. In my opinion, there has changed something in your app so the recorded xpath is no longer valid? As mentioned, without seeing the original/new xpath and Ranorex snapshot, there is not much anyone here can do for you..
At first, Ranorex 6.0.1 is too old and no longer supported, not to mention it's (along with 6.0.0) somewhat buggy I would strongly recommend to update to latest 6.2.1 (or at very least 6.1).
Additionally, without seeing the xpath of failing element, exact error message and Ranorex snapshot (NOT screenshot) of the failing element, it's next to impossible to tell what's wrong. In my opinion, there has changed something in your app so the recorded xpath is no longer valid? As mentioned, without seeing the original/new xpath and Ranorex snapshot, there is not much anyone here can do for you..
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
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
Re: Spy/Studio is not identifying a custom cntrl aftr AUT update
Hi,
I have attached both working and not working snapshots. The Object we are trying to identify is Container'_child' (you can check in working snapshot); same element is identified as element when AUT was upgraded.
We will try to upgrade to newer version soon, but we are trying to figure out the reason for this as AUT update was just a minor draft update and developers have confirmed that there is no change in that control between those drafts.
Regards,
Skeminje
I have attached both working and not working snapshots. The Object we are trying to identify is Container'_child' (you can check in working snapshot); same element is identified as element when AUT was upgraded.
We will try to upgrade to newer version soon, but we are trying to figure out the reason for this as AUT update was just a minor draft update and developers have confirmed that there is no change in that control between those drafts.
Regards,
Skeminje
Last edited by Skeminje on Tue Mar 28, 2017 1:00 pm, edited 1 time in total.
Re: Spy/Studio is not identifying a custom cntrl aftr AUT update
Hi,
I'm afraid, the snapshots are still missing. Additionally, please post the xpath of failing element (as stored in repository).
I'm afraid, the snapshots are still missing. Additionally, please post the xpath of failing element (as stored in repository).
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
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
Re: Spy/Studio is not identifying a custom cntrl aftr AUT update
Hi,
Yes. Upload failed as maximum allowed size is 1MB and each snapshot is more than 1MB.
XPath Working: /form[@wpfnative='True' and @title~'My\ A']/container/container[@automationid='LayoutRoot']/container[@automationid='MainAreaGrid']/container[2]/container/container[2]/element[@automationid='ScmApplicationHost' and @classname='ScmApplicationHost' and @orientation='None']/element[@automationid='ClrTabHost']/container/container[@controlname='_child']
XPath Not Working:/form[@wpfnative='True' and @title~'My\ A']/container/container[@automationid='LayoutRoot']/container[@automationid='MainAreaGrid']/container[2]/container/container[2]/element[@automationid='ScmApplicationHost' and @classname='ScmApplicationHost' and @orientation='None']/element[@automationid='ClrTabHost']/container/element[@controlname='']
Yes. Upload failed as maximum allowed size is 1MB and each snapshot is more than 1MB.
XPath Working: /form[@wpfnative='True' and @title~'My\ A']/container/container[@automationid='LayoutRoot']/container[@automationid='MainAreaGrid']/container[2]/container/container[2]/element[@automationid='ScmApplicationHost' and @classname='ScmApplicationHost' and @orientation='None']/element[@automationid='ClrTabHost']/container/container[@controlname='_child']
XPath Not Working:/form[@wpfnative='True' and @title~'My\ A']/container/container[@automationid='LayoutRoot']/container[@automationid='MainAreaGrid']/container[2]/container/container[2]/element[@automationid='ScmApplicationHost' and @classname='ScmApplicationHost' and @orientation='None']/element[@automationid='ClrTabHost']/container/element[@controlname='']
Last edited by Skeminje on Tue Mar 28, 2017 1:14 pm, edited 2 times in total.
Re: Spy/Studio is not identifying a custom cntrl aftr AUT update
OK, then please use DropBox, OneDrive or similar file sharing service and here post a link. BTW, make sure you saved compressed snapshot and eventually, reduce the size of snapshot as described here:
http://www.ranorex.com/forum/a-dynamic- ... ize#p38652
http://www.ranorex.com/forum/a-dynamic- ... ize#p38652
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
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
Re: Spy/Studio is not identifying a custom cntrl aftr AUT update
Looking at the xpaths you provided, apparently, the ending part of xpath is now different? 'Element' has been somehow replaced with 'Container' and also the controlname attribute is no longer empty, which I think is a welcome change?
NEW:
/container/container[@controlname='_child']
OLD:
/container/element[@controlname='']
NEW:
/container/container[@controlname='_child']
OLD:
/container/element[@controlname='']
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
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
Re: Spy/Studio is not identifying a custom cntrl aftr AUT update
Hi,
Its actually the reverse, Ranorex stopped identifying that object as container.
Old:
/container/container[@controlname='_child']
New:
/container/element[@controlname='']
Its actually the reverse, Ranorex stopped identifying that object as container.
Old:
/container/container[@controlname='_child']
New:
/container/element[@controlname='']
Re: Spy/Studio is not identifying a custom cntrl aftr AUT update
Ah sorry, then I got it wrong. If Ranorex now shows less information than before, then it's definitely not good. But as mentioned, without at least Ranorex snapshot, it's hard to tell what's wrong. And I think support folks would need to see your app (via remote session).
BTW, are you testing both versions of the app on the same machine?
BTW, are you testing both versions of the app on the same machine?
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
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