krestenbager
Occasional Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: Namemapping with extended find - invisible Alias?
Hi Alex, Thanks for the feedback! For our team a performance penalty would be OK given that we could see the Aliases of objects with extended find enabled. But others may have a different opinion :-) May I suggest a Project option alone the lines of "Use Alias on objects with extended find enabled during recording" [On/Off]. And also I would be very happy if you consider making a button of checkbox in the object spy window along the lines of: "Search for Alias in entire tree?" [On/Off]. This would allow most users to get the faster performance but also allow others to get the information that they need. Please consider this last suggestion as it would be very useful to us :-) Best regards Kresten1.2KViews0likes0CommentsRe: Namemapping with extended find - invisible Alias?
Hi Alex, Thanks for the input. Although this is a clever approach I don't think it will work for this particular AUT. The number of parent objects/levels do sometime change and also the path. So a child may have different parent objects from build to build. This is why the extended find option is really great except that it makes it difficult for out testers to create scripts. Best regards Kresten1.2KViews0likes0CommentsRe: Namemapping with extended find - invisible Alias?
Hi Dmytro, Thanks for the suggestion. I tried it but as luck would have it, it does not work with my AUT. Perhaps it is a MDI and thus parent/child relations are mapped in TC :-( So right now I am faced with three options: 1. Use extended find (and loose the ability to see which objects are mapped) 2. Use manpower to edit the namemapping with each new build (not really a practical option) 3. Try to implement a framework for binding UIDs with Aliases or global variables (sounds like a lot of wotk) 4. Forget about running smoketests until the AUT has stabilised (project management & developers will be unhappy) Again thanks to you all for your input, Kresten1.2KViews0likes0CommentsRe: Namemapping with extended find - invisible Alias?
Hi Dmytro, Ok so this seems to be a design decision from SmartBear. I see their point of view but it also means that, when going through the AUT, you cannot see if an object has an Alias or not :-( I agree with you that you should avoid the extended find if possible. Here is my problem: we would like to run a smoke test on a new build of our AUT without having to spend time on correcting the namemapping. We wish to run the smoketest as part of our Continuous Integration cycle so we need a procedure that is lightweight, dynamic and fast --> having to manually update the namemapping does not seem to fit this :-) Any suggestions you may have are very welcome as I don't quite know how to overcome this. P.s. I should mention that we have unique UIDs on all objects. I was thinking about making a script that would search the AUT for these UIDs and then try to link the Alias with this UID but it seems I would be making the namemapping functionality all over again - something I would rather not get into :-) Thanks for your input! Regards Kresten1.2KViews0likes0CommentsRe: Namemapping with extended find - invisible Alias?
Hi all, Thanks for the input. I have tried to clarify what I want to do and my problem. I have an application under development where the GUI elements move around from build to build. I want to create a namemapping that will allow me to run tests without having to do a new namemapping with each new build. My solution to this is to move my mapped objects up in the hiarchy to a point where there are no changes from build to build, i.e. a 'stable grand parent'. This works fine when I use the 'extended find' option. I am able to highlight the GUI element from both the Aliases panel and the Mapped Objects panel. Also when running a script I can access the GUI element by using the Alias. However the Object Spy will no longer show the Alias name for the GUI element. This is my problem. To illustrate the problem, try to follow these steps: 1. Create a new Suite 2. Create a new project 3. Record the following script (I use VB. and have set auto namemapping on) 4. Start Calc.exe 5. Click "4" button 6. Stop recording 7. You should now see the same as the included project "CalcNameMapping.zip" 8. Also please see 'TCalias_01_BeforeMoving.png' 9. For the 'btn' object in the namemapping, enable Extended find 10. In the 'Mapped Objects', move the 'btn' object to sit under the 'wndCalculator' object 11. Please see 'TCalias_02_AfterMoving.png'2.3KViews0likes0CommentsRe: Namemapping with extended find - invisible Alias?
Hi Margaret, If I enable 'extended find' and move the mapped object to a grandparent object I am not seeing what you see. Please see my attached image (TC_Aliases.png), marked with red arrows. I tried on the calc.exe application.2.3KViews0likes0CommentsRe: Namemapping with extended find - invisible Alias?
Hi Robert, Thanks for your input. Even if TestComplete needs to search for the object I would still expect a 'link' between the mapped object and the Alias. Another thing that confuses me is that you cannot click on a mapped object and 'Show Alias'. you can only go from the Alias and 'Show Mapped object'. Regards Kresten2.3KViews0likes0CommentsNamemapping with extended find - invisible Alias?
Hi all, It seems that when a mapped object has 'extended find' enabled and has been moved to a stable parent in the mapped objects tree, that the Object Spy is not able to identify the Alias for that object. From the Alias tree, 'Highlight on Screen' works fine and the script is able to use the Alias to access the object. But from the Object Spy, Mapped Objects tree and Object Browser there is no way to see if an object has an Alias. Is this an error in TestComplete or am I misunderstanding the functionality? Thanks! Regards Kresten25KViews0likes17CommentsGo to namemapping from script panel
Hi all, Just a thought for a future improvement: From the script workspace it would be nice to be able to right click on an Alias object and select "Go to namemapping". Sort of like the "Go to decelaration" but only it would jump you to the namemapping instead. Best regards Kresten Bager21KViews0likes1Comment