![gui map winrunner gui map winrunner](https://www.wisdomjobs.com/tutorials/to-manually-add-an-object-to-a-gui-map-file.gif)
So, WinRunner assigned the third property to both the buttons "MSW_id (Microsoft windows Id) which is assigned by operating system. WinRunner recorded the object logical names as OK and OK_1, in Physical description, both the buttons is having the same class and label properties. The Print dialog box, for example, is identified as a window with the label “Print” The physical description contains a list of the object’s physical Properties. WinRunner checks that there are no other objects in the GUI map with the same name. Usually WinRunner uses attached text that WinRunner can read as the Logical name. This is the name that appears in the test script when user records an application. This short name connects WinRunner to the object’s longer physical description. “Print” for a Print dialog box, or “OK” for an OK button. An Example of how WinRunner uses a logical name and physical description to identify an object: Each object is identified within the scope of its parent window, not the entire application. Instead, it learns the minimum number of properties to provide a unique identification of the object. When WinRunner learns the description of a GUI object, it does not learn all its properties. Each of these objects in the GUI Map file will be having a logical name and a physical description. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested. When WinRunner runs a test, it uses the GUI map to locate objects.
![gui map winrunner gui map winrunner](https://www.wisdomjobs.com/tutorials/viewing-gui-object-properties.gif)
These changes are then automatically propagated to all appropriate scripts, eliminating the need to build new scripts each time the application is modified.
![gui map winrunner gui map winrunner](https://slidetodoc.com/presentation_image/5f35410966138314d50cd4d3618b1f1e/image-23.jpg)
The GUI map provides a centralized object repository, allowing testers to verify and modify any tested object. WinRunner stores information it learns about a window or object in a GUI Map. The GUI map file contains the logical names and physical descriptions of GUI objects. GUI Map files are viewed in the GUI Map Editor. The GUI Map is made up of all currently loaded GUI Map files. “GUI Map” provides a layer of indirection between the objects described in the script and the widgets created by the application.