Subscription date : 07 March 2018
Messages : 1
|I have an application that uses the Docking & MDI component. I'd like to test this application using the Ranorex test suite but I'm hitting a problem. As described in my forum post on the Ranorex site (http://www.ranorex.com/forum/ranorex-fails-to-derive-xpaths-for-contents-of-tab-controls-t1887.html), when I open the application during a Ranorex recording, it's able to identify the contents of the front most tab in a ToolWindow. However, once I switch tabs, Ranorex can no longer determine paths to controls in the new front-most tab.
According to Ranorex, the issue is with how the ToolWindow contents are generated. Specifically, they're generated in such a way that automation tools cannot locate and identify the contents, thereby preventing the Ranorex tools from seeing them.
Is there something you can do to make the contents of the ToolWindow controls compatible with Ranorex's UISpy-like automation requirements? Or alternatively, a workaround you can propose? (possibly changing a template to provide automation information in a XAML attribute) I realize an update to the Docking control is on the horizon, but we're at a point in our ship cycle where we realistically can't take updates that require significant UI changes.
I'll be sending along a sample project that reproduces the issue.
Thanks very much,