TruthVoyager
New Contributor
Joined 7 years ago
User Profile
User Widgets
Contributions
Re: Cleaner automatic alias mapping
tristaanogre Thank you for the information and all your help. I understand the importance of mapping the whole tree. This request would not undermine that, it would just cut down on the extent of the tree that is aliased. If a middle man object, such as the panel that a button is in, is desired in the alias space, the user could simply drag the object down from the mapped objects list to include it in the alias space. I cannot see this being something that would be need too frequently. Whereas with the present set up, the extensive way TC populates the alias section results in a lot of cleaning post recording. Although I know that recording cannot alone be leaned upon for test creation, I believe there are ways it could be more useful in this regard. It would be great if recording could be more reliably used to flesh out a name map and better establish foundational steps from which to build a test; it would be nice if it resulted in a foundation that did not need as much post clean up and polish.1.7KViews0likes0CommentsRe: Cleaner automatic alias mapping
tristaanogre What do you mean when you say, "referencing certain attributes and contents that, while not something a user would interact with, are needed in order to validate certain functionality”? Are you referring to using the “previousSiblingElement” sort of identification properties? Furthermore, regarding the validation of certain functionality, doesn’t the Mapped Objects area handle this sort of functionality? You seem to be eluding to alias functionality that I am not sure I am aware of. So I could just be confused.1.7KViews0likes0CommentsCleaner automatic alias mapping
From what I can tell, mapping all of the parent objects is only really neccessary in the Mapped Objects section and not so much in the alias section. Therefore, it would be nice if only the page objects and the objects interacted with were mapped in the alias section or some other means of keeping the objects in the alias section down to the bare essentials.1.7KViews3likes5CommentsRe: Handling Reoccurring Objects (like navigation links)
tristaanogre While recording, will TC check project variables and, if an identification propety matches a project vairable, automatically set that mapped object to refrence the project variable? Or is this something that would need to be done manually?1.5KViews0likes0CommentsRe: Lockable Mapped Objects
tristaanogre The goal with the lockable feature is to make it so TC still mapps objects under those page objects that are not locked while overlooking the locked ones. Our application is very large, so to have to manually map every object would undermine the time saving potential of recording. I would like to see Test Complete's recording abilities become more reliable/useful so that we can be sure to reach our automation goals within our time goals. Perhaps I am not recognizing the true intended usefullnessof the recording tool. It appears to me that manual name mapping would undermine its usefullness. If not to map and create tests, what is the recording feature usefull for? I could see how it might be usefull after everything has already been mapped manually, but in large applications it would be a trumendous task.1.3KViews0likes0CommentsLockable Mapped Objects
A way I try to cut out duplicate mapped objects, like navigation links, is by having a parent page object wherein the URL consists of only the official name of the site capped with *s. I map all of my navication links to this page. However, when recording, Test complete will map every object under this one page object. Therefore, it would be nice if there was an objtion to set this object to be locked. Namely, the object is set so that children can only be added to it manually and not automatically.1.3KViews1like3CommentsHandling Reoccurring Objects (like navigation links)
It would save a lot of time in maintainance if there were a way to link identical objects that happen to be on different pages to one master object. Sort of like with templates but this controls the values. In other words, you may have several identical save buttons that would all inheret identification properties from one source. When the identificaton properties of the source are changed, so are all of the identification properties of the linked objects. This way if the identification properties of the save buttons were to change, we would not have to update every mapped save button one at a time, we could instead update them all at once by changing the source.1.6KViews0likes5CommentsCustomizable object naming conventions
It would save a lot of time, and go a long way towards readability, if users could establish naming conventions for Test Complete to implement while mapping objects. Perhaps as an extension of the templates feature where users would be able to set up how certain kinds of objects will be named. A button might be set up to be named via the following conventions: Part1(custom text)= "Tamplated", Part2(object property)= contentText, Part3(object property)= objectType, Part4(incamenting number)= start at 00. As a result, Test complete would name a save button "TemplatedSaveButton00" and or a nav link might be named "TemplatedAbout_UsLink00" with any spaces replaced by an underscore. Should another object happen to have the same naming properties as another the incramenting number would just incrament to give it a unique name. This would function similarly to the batch file naming capabilities of adobe bridge.506Views2likes0Comments