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 fo...
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
