Forum Discussion
You need to find some properties with which you can reliably identify the objects in your application.
You can also modify the properties used with wildcards (eg - Applic3 / Applic7 / Applic999 .... would all be covered by Applic*). However, be careful with this. If you had Applic3 and Applic7 on screen at the same time, using a wildcard would cause it to no longer be unique.
Recorded scripts/objects are a good starting point. But you can't rely on the automatic capture to give you robust, unique identification properties. If you want to use mapped objects, you pretty much always have to accept some manual intervention in mapping them if you want them to be robust long term.
Also - I don't think you're making best use of the Alias map.
Your look just like the full object map versions.
The point of the Alias map is to condense (get rid of container panels you don't really care about but that need to be there) and rename to make it more readable.
The full object map needs to be what it is. The Alias map should look more like representation of the parts of the screen the user (and you, as the automated test writer) actually care about.
eg:
Object: Browser.Page.Tab.Frame.Frame.Container.Panel.Panel.Button
I would Alias as:
Browser.Page.Tab.Button
(Assuming all the frames, containers and panels were just ways of splitting the screen up, but not things the user actually interacts with)
My Alias maps are MUCH smaller (and more legible) than my full object maps ...
Related Content
Recent Discussions
- 5 hours agojstaehlin
- 23 hours agoAivanitskiy