|
1)
How you integrated your automated scripts from TestDirector?
a)
When you work with WinRunner, you
can choose to save your tests directly to your TestDirector database or while
creating a test case in the TestDirector we can specify whether the script in
automated or manual. And if it is automated script then TestDirector will build
a skeleton for the script that can be later modified into one which could be
used to test the AUT.
2)
What are the different modes of recording?
a)
There are two type of recording in
WinRunner.
i.
Context Sensitive recording
records the operations you perform on your application by identifying Graphical
User Interface (GUI) objects.
ii.
Analog recording records
keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by
the mouse pointer across the screen.
3)
What is the purpose of loading WinRunner Add-Ins?
a)
Add-Ins are used in WinRunner to
load functions specific to the particular add-in to the memory. While creating a
script only those functions in the add-in selected will be listed in the
function generator and while executing the script only those functions in the
loaded add-in will be executed else WinRunner will give an error message saying
it does not recognize the function.
4)
What are the reasons that WinRunner fails to identify an object on the
GUI?
a)
WinRunner fails to identify an
object in a GUI due to various reasons.
i.
The object is not a standard
windows object.
ii.
If the browser used is not
compatible with the WinRunner version, GUI Map Editor will not be able to learn
any of the objects displayed in the browser window.
5)
What do you mean by the logical name of the object.
a)
An object’s logical name is
determined by its class. In most cases, the logical name is the label that
appears on an object.
6)
If the object does not have a name then what will be the logical name?
a)
If the object does not have a name
then the logical name could be the attached text.
7)
What is the different between GUI map and GUI map files?
a)
The GUI map is actually the sum of
one or more GUI map files. There are two modes for organizing GUI map files.
i.
Global GUI Map file: a single
GUI Map file for the entire application
ii.
GUI Map File per Test:
WinRunner automatically creates a GUI Map file for each test created.
b)
GUI Map file is a file which
contains the windows and the objects learned by the WinRunner with its logical
name and their physical description.
8)
How do you view the contents of the GUI map?
a)
GUI Map editor displays the content
of a GUI Map. We can invoke GUI Map Editor from the Tools Menu in WinRunner. The
GUI Map Editor displays the various GUI Map files created and the windows and
objects learned in to them with their logical name and physical description.
9)
When you create GUI map do you record all the objects of specific
objects?
a)
If we are learning a window then
WinRunner automatically learns all the objects in the window else we will we
identifying those object, which are to be learned in a window, since we will be
working with only those objects while creating scripts.
10)
What is the purpose of set_window command?
a)
Set_Window command sets the focus
to the specified window. We use this command to set the focus to the required
window before executing tests on a particular window.
Syntax:
set_window(<logical name>, time);
The logical name is
the logical name of the window and time is the time the execution has to wait
till it gets the given window into focus.
11)
How do you load GUI map?
a)
We can load a GUI Map by using the
GUI_load command.
Syntax:
GUI_load(<file_name>);
12)
What is the disadvantage of loading the GUI maps through start up
scripts?
a)
If we are using a single GUI Map
file for the entire AUT then the memory used by the GUI Map may be much high.
b)
If there is any change in the
object being learned then WinRunner will not be able to recognize the object, as
it is not in the GUI Map file loaded in the memory. So we will have to learn the
object again and update the GUI File and reload it. |
