Is there a way to perform an action at a position which is relative to the object AND not within the bounds object (perform an action on a secondary object which is located x/y distance away from the...
If your developers are still making changes to this control, then you should ideally push for the changes to be made, to either group the controls or provide an automation id. It will take less than a minute for the developers to implement this!
Thanks JDR2500 for the help. I was hoping there was some functionality in the keyword testing that could do this. The person who was asking prefers not to script if they can do without and it seemed like a common enough functionality need (for filling out forms/etc) that I thought the functionality would have made its way into the keyword arena.
In the nameMapping, it is easy enough to use the parent's properties as an identifier (see image below) ... but wasn't sure how to reference an object by one of it's sibling's properties. I'll play around with the name mapping a bit more.
If anyone knows if there is a way to do what I am trying to do via keyword functionality or name mapping properties, please let me know. Thanks in advance.
WPF, ugh. So many levels of hierarchy. Nevertheless, I think you should be able to accomplish what you want using well-constructed name mappings of all the levels. For each item in the level you'll need unique identifiers for the ID properties. That may require more than one. For example you might be able to use WPFControlName in combination with Uid. WPFControlOrdinalNo is another option. That one is an index. Consequently, there is risk it could change if your developers insert another control that increments the index number. Here is an example of a hierarchy and ID properties I've used:
There are some other tricks that can help with WPF. I didn't know about all of them when I got started and wasn't able to take advantage of the Simplified WPF object tree. That hides some of the WPF levels to make the name mappings more user friendly. Project Properties - WPF Options | TestComplete Documentation
It's worth reading as much as you can about using WPF with TestComplete.
With the right name mapping setup you should have no problem reliably targeting any WPF control in your application. It's a pain to create and you should not rely on the mappings automatically created during keyword testing. Go back to each one in the hierarchy. Use the Object Spy to identify good static unique properties and add them to the mapping. You can also use the Extended Find feature.
Once you get the hang of name mappings everything else will fall into place. Unfortunately, it seems your first experience will be with WPF controls. They are trickier in my experience due to the ridiculous depth of the hierarchy.
