ravi

• Jun 30th, 2006

 

For the Above the Question.........

By Default  (WinRunner) Capture the Object (Properities Methods Functions) in it's Golbal Map. It Can use in any Script by Calling it.

Per Test Map: Limited within the Prog or Script only. Can't use like Global Map.

pavan kumar singh

• Jul 11th, 2006

 

Winrunner has two types of recording mode --

1-Global GUI map file mode --by default winrunner recorded the  application by this mode .By this matheod all the recorded script save once and can be access for multiple use.  

2-Gui map file pertest mode --In Gui map file pertest mode , only the current recorded script will save . And for each recording for this mode need the saperate saving . 

Vennela

• Sep 7th, 2006

 

Hi! Straight to the point. Basically before we start testing an application, we should tell WinRunner what are the objects and their properties that the application hold. To do this we will traverse the application. This traversing(for the purpose to tell the WinRunner the objects in the application) can be done using WinRunner in two ways. 1) Global gui map -- In this mode, we are directing the WinRunner to learn about the objects and save them to the shared area in the WinRunner installation path. This gui file can be re-used for anyother test within the same application. 2) gui map per Test -- In this mode, WinRunner learns about the objects and automatically saves them to the default path. This is the default mode selected by the WinRunner. In this mode we do not need to save the gui explicitly.

sudhakar2068

 Profile 

• Sep 19th, 2006

 

Win Runner stores information it learns about a window or object  in   a GUI Map. When Win Runner runs a test, it uses the GUI Map to locate the objects. 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.

Each of these objects in the GUI Map will be having a logical name and physical description.

Global GUI Map file: GUI Map file for the entire application.

GUI Map File per test mode :Win Runner automatically creates a GUI Map file for each test created.

sudhakar kolla.

My Email:kollasudhakar2005@yahoo.co.in.

My Number:09819859346.

deep25kotwal

 Profile Answers by deep25kotwal 

• Oct 9th, 2015

 

Can somebody give information in case of using Selenium

GPT

• Sep 27th, 2023

 

Global Map per Test Mode:
When Reusability is a Priority: If you have common elements or functionalities that are used across multiple test cases, a global map can be beneficial. You define elements and their locators once, and multiple tests can refer to these global elements, promoting reusability and reducing maintenance efforts.
Centralized Maintenance: Global maps make it easier to maintain your test suite because changes to element locators or properties only need to be updated in one place. This reduces the risk of errors due to inconsistent element definitions across tests.
Efficiency: Global maps can save time and effort when dealing with shared elements by eliminating redundancy in element definition.
GUI Map per Test Mode:
Isolation and Independence: When you want each test case to be completely isolated from others, GUI maps per test mode can be a good choice. Each test case has its own set of element locators, reducing the risk of interference or side effects between tests.
Test Case-Specific Elements: In situations where test cases have unique or specific elements that are not reused in other tests, a GUI map per test mode makes sense. This keeps the element definitions closely tied to the test, making the test case more self-contained.
Parallel Execution: If you plan to execute test cases in parallel on multiple devices or browsers, GUI maps per test mode can help avoid conflicts and synchronization issues that might occur when using global maps shared across multiple test cases.