- Explain WinRunner testing process?-Winrunner testing process involves six main stages
- Create GUI Map File so that WinRunner can recognize the GUI objects in the application being tested
- Create test scripts by recording, programming, or a
combination of both. While recording tests, insert checkpoints where
you want to check the response of the application being tested.
- Debug Test: run tests in Debug mode to make sure they run smoothly
- Run Tests: run tests in Verify mode to test your application.
- View Results: determines the success or failure of the tests.
- Report Defects: If a test run fails due to a defect in the
application being tested, you can report information about the defect
directly from the Test Results window.
- What is contained in the GUI map? - WinRunner stores
information it learns about a window or object in a GUI Map. When
WinRunner runs a test, it uses the GUI map to locate 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 file will be having a logical name and a
physical description. There are 2 types of GUI Map files. Global GUI Map file: a single GUI Map file for the entire application. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.
- How does WinRunner recognize objects on the application? -
Ans:WinRunner uses the GUI Map file to recognize objects on the
application. When WinRunner runs a test, it uses the GUI map to locate
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.
- Have you created test scripts and what is contained in the test scripts?
- Yes I have created test scripts. It contains the statement in Mercury
Interactive’s Test Script Language (TSL). These statements appear as a
test script in a test window. You can then enhance your recorded test
script, either
|