Use my heavy extended find Name Mapping during record?
Hi All,
In order to make our Name Mapping more robust when handling our very dynamic test page that is currently under heavy development, we opted to use the Extended Find a lot when creating our Name Mapping.
Using extended find in Name Mapping has allowed us to remove all of the panels we don't want to depend on being there from the Name Mapping.
For example: Profile.Panel(0).Panel(1).Panel(0).Panel(0)... ... .Panel(1).Cell(4,0).Panel(0).EditButton.
Without having extended find on, if any of the properties that we are using to identify these panels changes, or a panel is removed, or a panel is added, then EditButton won't be found anymore. Instead of having that, we have Profile.EditButton, where all the panels inbetween we could care less about, and the extended find will search all children of Profile for the EditButton (which obviously has unique properties we can search on). This works better for us although it is slower when running.
However, by removing all of the said panels from the Name Map, when recording a script the Mapped Names are no longer used. This is a set back for us as we really wanted this feature to work. Infact if I use the Object Spy on an object that I know is mapped (using extended find), the Mapped Name property is blank.
Is there any way to make it so that TestComplete is still able to use the actual Mapped Names when recording, even though I am using Extended Find a lot in the Name Map?
In order to make our Name Mapping more robust when handling our very dynamic test page that is currently under heavy development, we opted to use the Extended Find a lot when creating our Name Mapping.
Using extended find in Name Mapping has allowed us to remove all of the panels we don't want to depend on being there from the Name Mapping.
For example: Profile.Panel(0).Panel(1).Panel(0).Panel(0)... ... .Panel(1).Cell(4,0).Panel(0).EditButton.
Without having extended find on, if any of the properties that we are using to identify these panels changes, or a panel is removed, or a panel is added, then EditButton won't be found anymore. Instead of having that, we have Profile.EditButton, where all the panels inbetween we could care less about, and the extended find will search all children of Profile for the EditButton (which obviously has unique properties we can search on). This works better for us although it is slower when running.
However, by removing all of the said panels from the Name Map, when recording a script the Mapped Names are no longer used. This is a set back for us as we really wanted this feature to work. Infact if I use the Object Spy on an object that I know is mapped (using extended find), the Mapped Name property is blank.
Is there any way to make it so that TestComplete is still able to use the actual Mapped Names when recording, even though I am using Extended Find a lot in the Name Map?
