You can create a GUI checkpoint using an existing GUI checklist. This is useful when you want to use a GUI checklist to create new GUI checkpoints, either in your current test or in a different test. For example, you may want to check the same properties of certain objects at several different points during your test. These object properties may have different expected values, depending on when you check them.
Although you can create a new GUI checklist whenever you create a new GUI checkpoint, it is expedient to “reuse” a GUI checklist in as many checkpoints as possible. Using a single GUI checklist in many GUI checkpoints facilitates the testing process by reducing the time and effort involved in maintaining the GUI checkpoints in your test.
In order for WinRunner to locate the objects to check in your application, you must load the appropriate GUI map file before you run the test.
For information about loading GUI map files, see “Loading the GUI Map File”.
To use an existing GUI checklist in a GUI checkpoint:
The Create GUI Checkpoint dialog box opens.
The Open Checklist dialog box closes and the selected list appears in the Create GUI Checkpoint dialog box.
WinRunner captures the current property values and a win_check_gui statement is inserted into your test script.
|
|
WinRunner Related Tutorials |
|
---|---|
LoadRunner Tutorial | HTML Tutorial |
QTP Tutorial |
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 |
All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.