Is there any way of stopping TC creating of Aliases by default when new elements are mapped.
TC produces a lot of elements we dont need, and we'd like to maintain the Alias map by adding as required into a fairly simplified UI Alias map.
Solved! Go to Solution.
No. Because Aliases are the preferred way of referencing an object, every time an object is mapped, an Alias is created. So, if you want to modify Aliases after mapping, that's a "step 2" in your mapping process.
That's the best approach, really. In my experience, while generally you don't need alot of those DIVs mapped, occasionally I've needed it to do some other detection or verification.
Modifying the Alias after the fact is relatively easy. Highlight the objects in the Alias tree, right click, and select "Exclude Items". This preserves the mapping for the identification engine but "telescopes" your Alias tree to something more manageable.
No. Because Aliases are the preferred way of referencing an object, every time an object is mapped, an Alias is created. So, if you want to modify Aliases after mapping, that's a "step 2" in your mapping process.
Thanks Robert.
I'd say that's a good idea for desktop apps but for java/REACT web pages with vast numbers of nested DIV containers which all gets mapped it prodces a lot of clutter we dont' need.
I'd like to maintain a high level alias structure like this:
Browser
>>Page
>>>>Content Container
>>>>>>Menu Container
>>>>>>>>Option 1
>>>>>>>>Option 2
>>>>Toolbar Container
>>>>Modal popups etc
Mapping a single button can produces 15-20 parent objects which is fine in Name Mapping but messes up Aliases.
I'lll have a go at the approach you mentioned and let you know.
Thanks
That's the best approach, really. In my experience, while generally you don't need alot of those DIVs mapped, occasionally I've needed it to do some other detection or verification.
Modifying the Alias after the fact is relatively easy. Highlight the objects in the Alias tree, right click, and select "Exclude Items". This preserves the mapping for the identification engine but "telescopes" your Alias tree to something more manageable.
I've seen that option but was to "afraid" to use it in case it broke too many tests.
We have a lot of legacy mapping in our our name map which needs removing as it's causing to many recogition issues and causing new mapped elements to be placed into the wrong part of the tree.
I've created a copy of our project with a deleted name map and will re-create it with the lessons learnt from our previous project and use the method you mentioned above to keep it trimmed down.
Thanks for your help with thiis. Much appreciated.
Hi,
Just to ensure that you are aware about Tools|Options|Engines|NameMapping|Map Object Names Automatically and Update Name Mapping During Test Run options.
I prefer to have them not checked and manually map only those elements that I need and control what properties are used for their identification.
Then I organize Aliases tree in a way that is convenient to me. (Robert's note about DIVs is perfectly valid.)
Subject | Author | Latest Post |
---|---|---|