if you have time and dont mind explaining the gui map editor, id be greatful.. mostly in saveing it to the right scriped. when i save i cant tell if its saveing to the open script or not.. what does the map editor do? and when saveing, does it save to each script file?
The GUI Map File is a text file containing the names and descriptions of all objects learned by WinRunner needed for proper record and playback. The GUI Map file can be edited at anytime in the GUI Map Editor. The GUI Map Editor is where you would learn all the objects and windows of
an application under test and it also displays the contents of the GUI map(all the windows and objects that have been learned).When your first learn object in the application the objects are stored in
a temporary file. To save what Winrunner has learned for the application click File/Save. To
call the gui map in the test script type Gui_Load(“c:\ “path”.mygui.gui).
Some clarification for you, keep in mind much of this is really preety
well covered by SQALogic.
The target of the Gui Map editor is a "FILE". This "FILE" will contain
all the objects you have learned through the Gui Map Editor. In fact
you should call this "target file" a GUi Map File (cuz thats what it is!)
So When you save what you are doing is saveing what is in memory to that
GUi Map File. You can employ the Gui Map editor to set the name of several
GUi Map File's to contain your object mappings of all the window controls
... and you want to be sure that you save often and esp before you
bring down WinRunner!
What I generally do is break up GUI Maps by project. So if I am
working on a project like "ProjectX" I tend to save and maintain
control information to a ever growing GUI Map File Called say
Projectx.gui. I am even such a fussy guy that I place the file in a
special common subfolder in my QA Local work area called:
..\GUI_Map so that file would be ..\GUI_Map\ProjectX.gui.
(..\GUI_Map really means a specific path like C:\QA\GUI_MAP)
But that covers organizational skills, what you want is to stick
to GUI Map Files. So when you write a script you link in that information
from the "Gui Map File" to your script via the function:
or to keep it simple assuming ..\GUI_Map == C:\QA\GUI_MAP
This will take that control information and load it into WinRunner's memory,
so that you can now use it!!! So this should clarify your pervious misnomer ..
you don't save GUi File info to scripts! You save it to a file and link that file to
Scripts, via the Gui_Load Function.
Here is what is so superior about the Gui Map concept. You are
mapping system information like a caption of a push button in a window
through a special identifier called a "logical name" which does not change
and is used by all your scripts that load Gui Map Files (yes more than one)
to get to the physical description of say that push button. If development
should change the caption of that pushbutton you can laugh at change in the face!
Because instead of going to every referance of every script and changing the info,
you go to one place .. THE GUI MAP FILE.
When you get there you don't change the "logical name" of the control but instead the
physical description. In our specific case you would change the caption of that
pushbutton. Now when your OLD script loads that NEW GUI Map File, your existing referance
to the "logical name" will map correctly to the new button with the new caption!!!
Learn this well because it is very powerfull.
[This message has been edited by rick_weth (edited 12-18-2000).]
Smoke me a kipper, I'll be back for breakfast!
Sr. QA Engineer