If you chose the Auto Merge option in the GUI Map File Merge Tool and there were no conflicts between files, then a message confirms the merge.
When you merge GUI map files automatically, conflicts occur under the following circumstances:
The following example demonstrates automatically merging two conflicting source files (before.gui and after.gui) into a new target file (new.gui).The GUI Map File Auto Merge Tool opens after clicking OK in the conflict warning message box,as described in “Preparing to Merge GUI Map Files”. It enables you to resolve conflicts and prevents you from creating new conflicts in the target file.
The conflicting objects are highlighted in red and the description of the conflict appears in a pane at the bottom of the dialog box.The files conflict because in both GUI map files, there is an object under the same window with the same name and different descriptions. Note that the windows and objects from the after.gui source file were copied to the new.gui target file without conflicts, since the new.gui file was initially empty.The names of the conflicting objects are displayed in red.
The source files are merged in the order in which they appear in the GUI Map File Merge Tool, as described in “Preparing to Merge GUI Map Files”.
To view the physical description of the conflicting objects or windows, click Description.
Each highlighted conflict can be resolved by clicking any of the following buttons. Note that these buttons are enabled only when the conflicting object/window is highlighted in both panes:
Once all conflicts between the current source file and the target file have been resolved, the source file is automatically closed and the next conflicting source file is opened. Once all conflicts between GUI map files have been resolved, the remaining source file and the target file are closed, and the GUI Map File Auto Merge Tool closes.
WinRunner Related Interview Questions
|SILK TEST Interview Questions||LoadRunner Interview Questions|
|WinRunner Interview Questions||HTML Interview Questions|
|QTP Interview Questions||Manual Testing Interview Questions|
|OpenStack Interview Questions||Automation Testing Interview Questions|
|API testing Interview Questions||Rational robot Interview Questions|
|Selenium IDE Interview Questions||Performance Testing Interview Questions|
|Test Director Interview Questions|
Winrunner At A Glance
Understanding How Winrunner Identifies Gui Objects
Understanding Basic Gui Map Concepts
Working In The Global Gui Map File Mode
Editing The Gui Map
Merging Gui Map Files
Configuring The Gui Map
Learning Virtual Objects
Checking Gui Objects
Working In The Gui Map File Per Test Mode
Working With Web Objects
Working With Activex And Visual Basic Controls
Checking Powerbuilder Applications
Checking Table Contents
Creating Data-driven Tests
Synchronizing The Test Run
Defining And Using Recovery Scenarios
Handling Web Exceptions
Using Regular Expressions
Enhancing Your Test Scripts With Programming
Creating User-defined Functions
Creating Compiled Modules
Calling Functions From External Libraries
Creating Dialog Boxes For Interactive Input
Understanding Test Runs
Analyzing Test Results
Running Batch Tests
Running Tests From The Command Line
Controlling Your Test Run
Setting Properties For A Single Test
Setting Global Testing Options
Customizing The Test Script Editor
Customizing The Winrunner User Interface
Setting Testing Options From A Test Script
Customizing The Function Generator
Initializing Special Configurations
Integrating With Quicktest Professional
Managing The Testing Process
Testing Systems Under Load
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.