Forum Discussion
You need to go up the heirarchy until it recognises an object correctly. Then add the new layer. Then add the existing mapped objects. (Assuming their identification properties have also remained valid) Your first example has two splitter panels, the second only has one?
Also wondering why you have all the intermediate container panels in your Alias map?
The point of the Alias map (in my eyes) is to give you a more readable map of your application.
In your case, I see a bunch of container panels which are required by the application, but are not likely to be addressed by you directly in a test. I wouldn't have those in the Alias tree myself.
eg:
Mapped as:
App
>Page
>>Panel
>>>Frame
>>>>Container 1
>>>>>Container 2
>>>>>>Container Button Panel
>>>>>>>Button 1
If I only ever needed button 1, my Alias map of that would likely be:
App
>Page
>>Button 1
Unless any of the intermediate panels made the map more readable, in which case using some of them can sometimes be desireable for readability if nothing else.
Thanks for the reply
I have Test Complete setup to auto name-map so everything you're seeing was done by test complete.
I''d love to trim it up a bit to make it easier to understand but there are countless areas of ourapp that has containers and sub containers inside that container and tabs inside that contaier that have their own containers etc.
So usng your example below, there's always something that gets used somewhere among hundreds of tests.
Do you have any suggestions on how to know what sections are not necessary? After years of writing scripts for our appication it seems no matter what I try and manually name map, it's already been mapped by Test Complete.
Thanks again for the reply, really appreciate it.