1 / 14

What is WinRunner

What is WinRunner. WinRunner is Mercury’s legacy automated testing tool It is similar to QTP in functionality WinRunner integrates with other Mercury testing solutions including: TestDirector/Quality Center QTP LoadRunner Utilizes an add-in architecture for compactness and extensibility.

benoit
Download Presentation

What is WinRunner

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. What is WinRunner • WinRunner is Mercury’s legacy automated testing tool • It is similar to QTP in functionality • WinRunner integrates with other Mercury testing solutions including: • TestDirector/Quality Center • QTP • LoadRunner • Utilizes an add-in architecture for compactness and extensibility

  2. WinRunner Environment • Windows • C++, Visual Basic, Java, Powerbuilder, Stingray, Smalltalk • Web • Web Applications • Other technologies • SAP, Siebel, Oracle, Peoplesoft, ActiveX

  3. WinRunner Add-ins • ActiveX Controls - For testing software written using ActiveX (also known as COM) technology. This technology allows people to create objects in one language and use those objects within other languages/applications • Visual Basic - For applications written in the Visual Basic language • PowerBuilder - For applications written in the PowerBuilder language • WebTest - For testing web applications written in any language. In web applications, we interact with the application though a web browser and so the web application can be written in any language.

  4. Testing Process • Create GUI Map • Create Tests • Record • Edit • Insert checkpoints • Insert synchronization points • Parameterize test • Include TSL code • Debug test • Run tests

  5. WinRunner Object Identification Process • GUI Configuration Tool • The tool determines what properties of objects are recorded • GUI Spy • Allows users to view the property of an object without recording it • GUI Map Editor • Holds information recorded about each object allowing the test to identify the object during execution

  6. Creating a GUI Map • Per Test • A GUI Map is created for each test • Global • A single GUI Map is used for multiple tests

  7. CREATE TEST [STEP 2] • Record Steps • Edit • Insert synchronization points • Insert checkpoints • Parameterize values • Include TSL code

  8. Record • Read the outline of steps to perform • Practice performing the steps to minimize error • Choose record mode • Context Sensitive • Analog • RECORD • Stop, Save test, playback

  9. Edit Test • Insert synchronization points • Used to slow down execution of a test script • Checkpoints • Used to checkexpected value of a step against the actual value at a specific point during execution • Insert Parameterization • Allows you to store data in the data table • Include TSL code • Last option. Very powerful.

  10. Synchronization Point • Specific time • Uses the wait function to pause the test for a specific amount of time [in seconds] • Until an event occurs • Pauses until a specific property of an object has a specific value

  11. Checkpoints • GUI • Checks multiple properties of a single object • Text • Checks part or all the text within an object • Bitmap • Checks the visual layout of an entire object or a portion of the object • Database • Checks data in the database

  12. Parameterize Data • Allows your test to read data from the data table. • The data table is an Excel spreadsheet file editable from using Excel or any other application that can edit a .xls document • The columns can be renamed by double-clicking on the header of the column.

  13. TSL Coding • When the tools provided by WinRunner are not sufficient to test an application, TSL coding can be used. • TSL is a proprietary language only used within Mercury tools.

  14. Recap • Checkpoints - check • Synchronization points - wait • Parameterization – configuration data • TSL – adds programmable logic

More Related