The document discusses the WinRunner testing process and how it identifies GUI objects. It explains that WinRunner uses the Rapid Test Script Wizard to learn object descriptions, which it saves in a GUI map file. This file is then used to identify and locate objects when running tests. The document also discusses how tests identify objects using logical names rather than full physical descriptions, and how data-driven testing works by checking multiple sets of data using functions like ddt_open, ddt_close, and ddt_set_row.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
61 views14 pages
WINRunner Class 2
The document discusses the WinRunner testing process and how it identifies GUI objects. It explains that WinRunner uses the Rapid Test Script Wizard to learn object descriptions, which it saves in a GUI map file. This file is then used to identify and locate objects when running tests. The document also discusses how tests identify objects using logical names rather than full physical descriptions, and how data-driven testing works by checking multiple sets of data using functions like ddt_open, ddt_close, and ddt_set_row.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14
The WinRunner Testing Process
How Does WinRunner Identify
GUI Objects?
GUI application are made up of GUI objects such
• as windows,buttons,lists and menus.
Rapid Test Script Wizard,Which learns the
• description of all the GUI objects.
It saves the object descriptions in GUI map file.
When we run tests,WinRunner uses this file to
• identify and locate objects. Understanding the GUI Map
• The GUI map is actually the sum of one or more
GUI map files.
• There are two modes for organizing GUI map
files:
• Global GUI Map File Mode.
• the GUI Map File per Test Mode. How a Test Identifies GUI Objects • WinRunner identifies each GUI object in the application being tested by its physical description: a list of physical properties and their assigned values.
• These property–value pairs appear in the
following format in the GUI map:
{property1:value1, property2:value2, property3:value3, ...} • For example, the description of the “Open” window contains two properties:
• class and label. In this case the class property has
the value window, while the label property has the value Open: – {class:window, label:Open}
• The class property indicates the object’s type. Each
object belongs to a different class, according to its functionality: window, push button, list, radio button, menu, etc. Logical Names
• In the test script, WinRunner does not use
the full physical description for an object. Instead, it assigns a short name to each object: the logical name.
• The logical name is the label that appears
on an object:
• for a button, the logical name is its label,
such as OK; Getting Started with RapidTest
• Spying on GUI Objects (Gui spy)
Help us to understand how WinRunner identifies GUI objects. Synchronizing Tests When should you synchronize?
• To retrieve information from a database
• For a window to pop up • For a progress bar to reach 100% • For a status message to appear Creating Data- Driven Tests About Creating Data- Driven Tests
• When you test your application, you may want to
check how it performs the same operations with multiple sets of data.
• For example, suppose you want to check how
your application responds to ten separate sets of data. The Data- Driven Testing Process Creating a Data- Driven Test
DataDriver Wizard Modify your test script
manually. Using TSL Functions with Data- Driven Tests • ddt_ open : Function creates or opens the specified data table.
ddt_open(data_table_name,mode);
• ddt_ close : Function closes the specified
data table. ddt_ close ( data_ table_ name );
• ddt_ set_ row : Sets the active row in the specified