This blog provides a sample for a custom UIAutomation provider.
Microsoft’s UISpy looks specifically and only at the UIAutomation interface of an application. Ranorex Spy on the other hand interfaces MSAA through an according plugin, but not UIAutomation directly.
UIA is used to interact with WPF controls only, but there is no plugin for UIAutomation alone.
Therefore custom UIAutomation is not fully supported on non-WPF controls.
But every UIAutomation-enabled application automatically also provides the MSAA interface. The number of properties are reduced, though. From the remaining MSAA properties the Ranorex Plugin filters out those that are not important for the GUI automation.
The amount of filtering is reduced a bit in Ranorex 3.0 with respect to Ranorex 2.3.x.
There is a way to disable the filtering through code:
However, for this to work with Ranorex Spy, one needs to create a simple plugin and add the code there.
Code: Select all
MsaaFlavor.Instance.FilterEnabled = false;
Read the following forum entry for more on this.