I have been using WinRunner to test a Web based application that has been developed in a number of iterations and have found that having a Global GUI map is the best way to go for the following reasons.
1. With each new iteration we receive there tends to be some changes made to the location of objects; ie. A surname field on a Customer screen will be location 5 in one iteration and then location 2 in the next iteration. To make matters even more confusing, the objects in our application do not contain tags thus when you record for example the surname field, it is displayed in the script as edit_2 and of course this can end up as being edit_5 in a new iteration.
The Global Map method has been best for us because I modify each object saved to the Global map, giving it a logical name. (edit_2 becomes Surname.
Then if I cannot playback a script in a new iteration because the location has changed, all I have to do is update the Global map instead of updating X number of seperate Map per Test scripts.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by c.rajarajan: Dear,
We have two options of recording.
1.Global GUI Map File
2.GUI Map File per Test.
We have tried little with the second one but we don't know about the first option.
Can anyone give us some information about Global GUI Map File.Which one will be better.
Don't know which version of WinRunner you are using, but the User's Guide for 7.5 has a separate chapter for both Global Gui Map File mode (chapter 5) and for GUI map file per test mode (chapter 6). You might want to consider taking a step back and (re-)reading those two chapters. It's a good place to start...and then come back with questions for further clarification.
And while we're at it, you might want to take a larger step back and review chapter 4 as well (Understanding Basic GUI Map Concepts). This all flows under Part II: Understanding the GUI Map.