jpr348
Occasional Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Re-applying Templates
Thanks for that. The Aliases are OK so long as the name mapping structure does not change too much. I'm in the process of removing unecessary extended find objects and increasing the number of properties to make our suite more faster and more reliable. Removing extended find means the mapped objects are also in a very different location in the mapping tree. The Alias doesn't seem to work in this case. It would be good if the Alaises can be orginised in a totally arbritary way and create our own folders/sections.1.5KViews0likes2CommentsRe: Is it possible to disable "Find this node on any level of NameMapping tree"?
Please disregard the above. Sorted it. The problem was the option "Use extended find when possible" was enabled and greyed-out due to the "Map object names automatically" being disabled. Steps: "Use extended find when possible" (Is greyed-out) Enabled "Map object names automatically" Disabled "Use extended find when possible" (Not greyed-out) Disabled "Map object names automatically" "Use extended find when possible" (Is greyed-out) Got everything mapping normally now without extended find.1.4KViews1like1CommentIs it possible to disable "Find this node on any level of NameMapping tree"?
When manually mapping new objects "Find this node on any level of NameMapping tree" is enabled by default. Is there anyway to set the default to disabled? We have a fairly extensive namemap and if enabled TC places the object somewhere buried in the parent hierarchy. We then have to find it and manually drag it into the correct location and recreate the Alias. This option is also applied automatically when TC prompts to map parent objects automatically. Over time, the end result is an out of control namemapping tree. Extended find is only used where necessary and in limited areas of our UI like dynamic grids or UI structure dependent on data. It is useful but should not be used for every node. I have disabled Extended Find in the name mapping options (See screenshot) but it still appears enabled. We are using name mapping templates but there are no options there to control this either. How can I disable this option?Solved1.4KViews0likes2CommentsRe: Feature Request "Add object here" to allow adding an object at a top-level well identified node
Thanks. That does work. I noticed TC always has the "allow this option to be found at any level" checkbox enabled by default and the resulting mappings are not attached to it's parent but some other top level parent. (Using extended find causes us problems and messes up our name mapping so I've stopped using it except as an absolute last resort where no static mappings cannot be used.) Also by default TC extremelly sparse ID's when automatic mapping is used which along with extended find is a recipe for mis-recogition. I've started to use templates with an increased numbers of properties which has massively improved the reliabilty of object recognition and speed of testing.1.2KViews0likes0CommentsFeature Request "Add object here" to allow adding an object at a top-level well identified node
It would be really usefull if the object spy could be made to work relative to a specified node in the name mapping. Eg Right-clicking a well identified node and selecting "add object here" which then opens the spy tool. Extended-find will then be used to ensure the object is found at test-run-time. As it is TC forces new mappings to map objects, creating upteen parent DIV/Panel objects with little or no identifable properties which then must be carefully removed afterwards. If not they clutter the object map and cause problems at test-run-time or when new objects are added, duplicated objects for instance. This allows a top-down approach to be used to manage the object map rather than the bottom-up approach inherent in the Spy tool.Solved1.3KViews0likes3Comments