Hi,
How to improve the performance of Ranorex tool in identifying WPF elements. Global plugin settings don't seem to make anything better. Is there anything I need to do specifically or generally inorder to improve the performance. Any thoughts?
Thanks,
Jenny
Identifying WPF elements
Re: Identifying WPF elements
Hi Jenny,
Unfortunately, it's pretty hard (next to impossible) to suggest something reliable, without knowing more details about your AUT (ideally working sample app) and exact problem you are experiencing. What xpaths do you use (post an example of slow to find xpath)? Could you please post a snapshot from your app? Slow identification of controls usually means that the xpath is too much simplified or too generic. Please post some xpath examples and snapshot so we can suggest better xpaths.
Unfortunately, it's pretty hard (next to impossible) to suggest something reliable, without knowing more details about your AUT (ideally working sample app) and exact problem you are experiencing. What xpaths do you use (post an example of slow to find xpath)? Could you please post a snapshot from your app? Slow identification of controls usually means that the xpath is too much simplified or too generic. Please post some xpath examples and snapshot so we can suggest better xpaths.
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
