| || |
GUI Map vs GUI description in scripts
I have already created scripts, and have just one big GUI Map. At this point I feel the need that it might not be the most feasible option in my case. Reason:
1. I have many same Objects that just belong to different windows.
2. These Objects are not just located in one position, their location and name attribute can change depending on the page loaded. Within the page there are excel sheet type tabs; Sheet1, Sheet2, Sheet3, etc. So within the page itself they can be anywhere in one of the Sheets. All this information is gathered from the data base.
I was thinking of using excel sheets to create an application map that would contain information about such objects like location and name, reading it from the database. Is this a good approach? how much would it slow me down? Is there an alternative approach that would be more feasible. Any suggestions would be appreciated.
Thanks very much,
Re: GUI Map vs GUI description in scripts
Use GUI maps and descriptions.
I created an automated test system for a rather stable app.
Many buttons were the same from window to window (same everything except window). Even windows were the same (type, not name) from module to module.
I created global associative arrays containing physical descriptions.
On the other-hand for the menu system of many of the windows, I retained the GUI map.
Depending on the situation, I could use