Praveen Tutorials

 The first stage is to create the GUI map so WinRunner can recognize the GUI objects in the application being tested. ➢ Use the Rapid Test Script wizard to review the user interface of your  application and systematically add descriptions of every GUI object to the GUI map ➢ Alternatively, you can add descriptions of individual objects to the GUI map by clicking objects while recording a test The GUI Map is made up of all currently loaded GUI Map files. GUI Map files are viewed in the GUI Map Editor. The GUI map file  contains the logical names and physical descriptions of GUI objects. WinRunner stores information it learns about a window or object in a GUI Map. 

WinRunner Testing Modes  ➢ WinRunner facilitates easy test creation by recording how you work on your application.  ➢ As you point and click GUI (Graphical User Interface) objects in your application,  ➢ WinRunner generates a test script in the C-like Test Script Language (TSL).  ➢ You can further enhance your test scripts with manual programming.  ➢ WinRunner includes the Function Generator, which helps you quickly and easily add functions to your recorded tests The WinRunner Testing Process 1. Create GUI Map 2. Create Tests 3. Debug Tests 4. Run Tests 5. View Results 6. Report Defects

 If you have ever tested software manually, you are aware of its drawbacks.Manual  testing is time-consuming and tedious, requiring a heavy investment in human  resources. Worst of all, time constraints often make it impossible to manually test every  feature thoroughly before the software is released. This leaves you wondering whether  serious bugs have gone undetected.   Automated testing with WinRunner addresses these problems by dramatically  speeding up the testing process. You can create test scripts that check all aspects of  your application, and then run these tests on each new build. As WinRunner runs tests,  it simulates a human user by moving the mouse cursor over the application, clicking  Graphical User Interface (GUI) objects, and entering keyboard input—but WinRunner  does this faster than any human user.