Solved
Namemapping nightmare
Hi, I am new to Testcomplete and having trouble with namemapping. I am using Testcomplete to test a WPF based application. The issue is that UI on the application keeps changing, and each time ...
Forum Discussion
I don't think you all understand how painfull it is to write scripts for testing WPF applications, specially large ones.
WPF by nature wraps every single control with many layers of useless things (useless for testing purposes). Now.... this things are the ones that make finding things difficult.
In my case I have to use both mapping and searching tools in order to find objects.
Those I can mapp well... they are the easiest.
Those I have to find.... not always have a good result.
I'll give you an example:
in this example tree
|- region
|- wrapper
|- button
|- wrapper
|- wrapper
|- name = "Button1"
when you search using FindAllChildren you look for the button name right? Well the function returns the actual path to the name property or if you are lucky the parent (wrapper). Now the wrapper is not clickable since is not visible or enabled (sometimes) which makes it really difficult to climb up in the tree since there's not FindParent method to call.
Now HD, try to mapp as much as you can. Make sure you don't mapp properties that change every time you run the program and for searching purposes try to make your own functions calling FindAllChindren inside, so you can add parameters and search from different parts in the tree.
Good luck
WPF by nature wraps every single control with many layers of useless things (useless for testing purposes). Now.... this things are the ones that make finding things difficult.
In my case I have to use both mapping and searching tools in order to find objects.
Those I can mapp well... they are the easiest.
Those I have to find.... not always have a good result.
I'll give you an example:
in this example tree
|- region
|- wrapper
|- button
|- wrapper
|- wrapper
|- name = "Button1"
when you search using FindAllChildren you look for the button name right? Well the function returns the actual path to the name property or if you are lucky the parent (wrapper). Now the wrapper is not clickable since is not visible or enabled (sometimes) which makes it really difficult to climb up in the tree since there's not FindParent method to call.
Now HD, try to mapp as much as you can. Make sure you don't mapp properties that change every time you run the program and for searching purposes try to make your own functions calling FindAllChindren inside, so you can add parameters and search from different parts in the tree.
Good luck