

#Winrunner test script language software
You can also create reports and graphs to help review the progress of planning tests, running tests, and tracking defects before a software release.ġ1) How you integrated your automated scripts from TestDirector?Ī.
#Winrunner test script language manual
With TestDirector you can create a database of manual and automated tests, build test cycles, run tests, and report and track defects. It helps quality assurance personnel plan and organize the testing process. TestDirector is Mercury Interactive’s software test management tool.

This information is sent via e-mail to the quality assurance manager, who tracks the defect until it is fixed.ġ0) What is the use of Test Director software?Ī. 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. 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.

The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. Following each test run, WinRunner displays the results in a report. If any mismatches are found, WinRunner captures them as actual results.ĩ) How do you analyze results and report the defects?Ī. 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. We run tests in Verify mode to test your application. We can also debug script using the Step, Step Into, Step out functionalities provided by the WinRunner.Ī. We can debug the script by executing the script in the debug mode. Yes, I have performed debugging of scripts. 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.ħ) Have you performed debugging of the scripts?Ī.

You can then enhance your recorded test script, either by typing in additional TSL functions and programming elements or by using WinRunner’s visual programming tool, the Function Generator.Ħ) How does WinRunner evaluate test results?Ī. These statements appear as a test script in a test window. It contains the statement in Mercury Interactive’s Test Script Language (TSL). 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?Ī. When WinRunner runs a test, it uses the GUI map to locate objects. WinRunner uses the GUI Map file to recognize objects on the 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?Ī. Global GUI Map file: a single GUI Map file for the entire application Each of these objects in the GUI Map file will be having a logical name and a physical description. 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. WinRunner stores information it learns about a window or object in a GUI Map. 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.Ī. View Results: determines the success or failure of the tests. Run Tests: run tests in Verify mode to test your application. Debug Test: run tests in Debug mode to make sure they run smoothly While recording tests, insert checkpoints where you want to check the response of the application being tested. Create test scripts by recording, programming, or a combination of both. Create GUI Map File so that WinRunner can recognize the GUI objects in the application being tested
