Recording a Test To Record a Test in WinRunner, Select the Record Button from the Standard Toolbar Starting WinRunner To start WinRunner, click Start > Programs > WinRunner > WinRunner Recording User ActionsĬreating a New test Click on New Test Recording User Actions The application contains bitmap areas (such as a drawing area) Exact mouse movements are required The application contains GUI objects Exact mouse movements are not required You plan to reuse the test in different versions of the application Choose Analog if. WinRunner generates following TSL statements button_press (“ OK ”) move_locator_track (1) mtype ('-') mtype ('+') Ĭhoosing a Recording Mode Choose Context Sensitive if. if you record a mouse click on OK button. WinRunner generates following TSL statements- Analog Mode Analog Mode Records the exact coordinates traveled by the mouse For e.g.
Recording Mode Context Sensitivity Context Sensitivity records operations in terms of GUI objects. WinRunner Testing Process 4 Run Tests Run tests in Verify mode to test your application It compares the current data of the application being tested to the expected data captured earlier If any mismatches are found, WinRunner captures them as actual results 5 View Results After each test run, 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 6 Report Defects If a test run fails due to a defect in the application being tested it can be reported 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 WinRunner Testing Process 1 Create the GUI Map WinRunner must learn to recognize the objects in an application in order to run tests The preferred way to teach WinRunner your objects depends on the GUI map mode 2 Create Tests WinRunner writes scripts automatically when recording actions in applications One can program directly in Mercury Interactive’s Test Script Language (TSL) 3 Debug Tests You debug the tests to check that they operate smoothly and without interruption
MERCURY WINRUNNER PRICE MANUAL
Automated Testing Manual Testing: Is time-consuming and tedious Requires a heavy investment in human resources Time constraints often make it impossible to manually test every feature thoroughly before the software is released Automated Testing: Dramatically speed up the testing process Creation of test scripts which check all aspects of the application Execute these tests on each new build īenefits of Automated Testing Fast: Run tests significantly faster than human users Reliable: Tests perform precisely the same operations each time they are run, thereby eliminating human error Repeatable: You can test how the software reacts under repeated execution of the same operations Programmable: You can program sophisticated tests that bring out hidden information from the application Comprehensive: You can build a suite of tests that covers every feature in your application Reusable: You can reuse tests on different versions of an application, even if the user interface changes Prior to a software release, you can run these tests in a single overnight run- enabling you to detect and ensure superior software quality.Winrunner Training Objective of the Course Understand the benefits of automated testing To get an insight into the working of automated test tools To use and understand the features of Winrunner Creation of test scripts using Winrunner īenefits of Automated Testing WinRunner Testing Process WinRunner Recording Mode Working with other Test Suite Tools You create adaptable and reusable test scripts that challenge the functionality of your application. Winrunner helps you automate the testing process, from test development to execution. It is used to quickly create and run sophisticated automated tests on your application. WinRunner, Mercury Interactive’s enterprise functional testing tool. WinRunner LoadRunner Test Director Silk Test Test Partner
0 kommentar(er)
