WinRunner

WinRunner is used for creating automate script for GUI, funcional and regression testing.

WinRunner test procedure:

a. WinRunner test involves these six head phases

i. Create GUI Map Files so that WinRunner can recognize the GUI objects in front of the use to be tested

ii. 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.

iii. Debug Test: Run Tests in Debug mode to make sure they run smoothly without any problems.

iv. Run Tests: run tests in Verify mode to test the application.

v. View Results: Determines the success or the failure of the tests.

vi. 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.

Detail of GUI map:

WinRunner uses the GUI map file to recognize objects on the application. If WinRunner runs a test, it uses the GUI map to be objects. It reads the description of an object in front of the GUI map and then appearance for an object with the same property in front of the application to be tested. a. WinRunner stores information that it learns about a window or object of a GUI map. If WinRunner runs a test, it uses the GUI map to be objects. It reads the description of an object in front of the GUI map and then appearance for an object with the same property in front of the use to be tested. Each of these objects in front of the GUI map file will have a logical name and a physical description.

b. There are two types GUI map files.

i. Global GUI map file : A single GUI map file for the entire use

ii. GUI map file per test: WinRunner automatically creates a GUI map file for each test created.

Test scripts:

Test scripts 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 the recorded test script, either by typing in additional TSL functions and programming elements or by using WinRunner’s visual programming tool, the Function Generator.

Test scripts can be run by following method:

a. We run tests in Verify mode to test the application. Each time WinRunner encounters a checkpoint in the test script, it compares the current data of the application being tested to the expected data captured earlier.

b. If any mismatches are found, WinRunner captures them as actual results.

Debugging of the scripts:

Debugging of scripts can be perform by executing the script in the debug mode. We can also debug script using the Step, Step Into, Step out functionalities provided by the WinRunner.

Process of analyzing results and reporting the defects:

WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window. 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. This information is sent via e-mail to the quality assurance manager, who tracks the defect until it is fixed.