Remapping Issues. Inconsistencies.
I have a question that have been bothering since I started using TestComplete in August. This issue seems to come back more and more often. Hi all! Happy New Year! We have couple of website...
Forum Discussion
Well, it depends upon what needs to be done in the remap... Do you need to change properties? Are there new DIV (Panel) objects that weren't there before? Etc.
As I mentioned elsewhere, we just recently had to do something similar. A new version of bootstrap was applied to our application which changed a few properties here and there and added some new DIV panels in the hierarchy.
If it's just properties that need to change, you should investigate if there's some set or properties that maintain value consistently and use those. Alternatively, you could work with your development team and have them help you out by making sure that there's a consistent set of properties for you to use.
If it's additional panels that are being added in (or removed) Look into using some judicial placements of the "Extended Find" checkbox.
Say, for example, I have something mapped like
NameMapping.Sys.browser.MyPage.MyPanel.Panel1.Panel2.MyTextBox
Then a new version is pushed through and, between Panel1 and Panel2, there's now some new panel there. Your solution could be, simply, to click the "Extended Find" checkbox on the Panel2 mapped object. Then it doesn't matter how many Divs there are between Panel1 and Panel2, it will find it.
Finally.... and this I'm not clear on because your screenshots point out Aliases but we don't see the actual mapping part... but keep in mind that there's a difference between an Alias and a mapped object. The Mapped object is how TestComplete identifies it and starts with NameMapping.Sys at the root. This is the full hierarchy and object identification structure you've defined. Aliases are an "in between" layer between the NameMapping engine and your code. Each alias points to a NameMapping object. So, when you reference an Alias in your code, the tool goes to that Alias and references the NameMapping object to make the identification.
What this means is that you can re-organize your NameMapping hierarchy and properties as I described above.... but so long as the Aliases don't change, you should never need to touch your code.
