Winrunner Software Testing Tool

Posted on
TestingWinrunner Software Testing Tool
  1. Q #14) Explain the WinRunner testing process? Answer: The WinRunner testing process involves six main stages: Create a GUI Map File so that WinRunner can recognize the GUI objects in the application.
  2. Winrunner Testing Tool Software Load Testing Tool Screensaver v.1.0 This is a free screensaver from Neotys. We will test your web application under real stress using an easy and powerful load testing tool.
  3. Software Search For winrunner testing tool winrunner testing tool In Title No results were found containing winrunner testing tool In Title Sponsored Links winrunner testing tool In Short Description No results were found containing winrunner testing tool In Short Description winrunner testing tool In Long Description 4.2 making it easier to get to the sites you need; tools.
(Redirected from WinRunner)
HP WinRunner
Developer(s)HP/Mercury Interactive
Stable release
Operating systemMicrosoft Windows
Typetest automation
WebsiteHP Functional Testing software web page

HPWinRunner software was an automated functional GUI testing tool that allowed a user to record and play back user interface (UI) interactions as test scripts.

Winrunner software testing tool free download for windows 7

As a functional test suite, it worked with HP QuickTest Professional and supported enterprise quality assurance. It captured, verified and replayed user interactions automatically, in order to identify defects and determine whether business processes worked as designed.

WinRunner is an Automation Software Testing Tool that is owned by HP and was developed by Mercury Interactive. It is known and extensively used for its ability to supports the majority of the programming languages and web development technologies such as C, C, C#, Visual Basic, VC, D2K, Java, HTML, Power Builder, Delphe, Cibell, etc. Welcome to WinRunner, Mercury Interactive’s enterprise functional testing tool for Windows 95, Windows 98, Windows NT 4.0, Windows 2000, and Windows Me. This guide describes everything you need to.

The software implemented a proprietary Test Script Language (TSL) that allowed customization and parameterization of user input.

HP WinRunner was originally written by Mercury Interactive.[1] Mercury Interactive was subsequently acquired by Hewlett Packard (HP) in 2006.[2] On February 15, 2008, HP Software Division announced the end of support for HP WinRunner versions 7.5, 7.6, 8.0, 8.2, 9.2—suggesting migration to HP Functional Testing software as a replacement.[3]

Winrunner Software Testing Tool Free Download

Helping Guides[edit]

Open Source Frameworks for WinRunner[edit]

  • SAFS (Software Automation Framework Support)
  • EMOS-Framework (GUI Modeling)

See also[edit]

External links[edit]

Winrunner software testing tool free download for windows 7


  1. ^ 'WinRunner FAQ.' Retrieved 2010-03-25.
  2. ^HP news release: “HP Closes Landmark Mercury Acquisition” Nov. 2006
  3. ^“End of Support announcement HP WinRunner 7.5, 7.6, 8.0, 8.2, 9.2 (all editions).” Retrieved 2010-03-25.
Retrieved from ''

QTP vs WinRunner

Both WinRunner and QTP are programs that have been developed by HP’s software division mainly for testing purposes. WinRunner is software that is tasked to perform Graphic User Interface (GUI) testing and is also allowed to record and play back user interface interactions as test scripts. QTP, on the other hand, refers to Quick Test Professional, which is a product that has been developed for the provision of regression and functional test automation on different software environments. Software quality assurance testing also heavily relies on QTP. Both WinRunner and QTP come with functional differences relating to the tasks they perform and these are elaborated in detail below.

When it comes to the environment that is supported by both WinRunner and QTP, these two differ greatly. WinRunner supports an environment that has Powerbuilder, Delphi, Centura, Stingray, Forte, and SmallTalk. The environment that QTP works on includes .NET framework, Flash and XML web services.

The user model is also an issue of difference. This deals with the way in which users interact with the application. With WinRunner users will interact with a focus on the test script, looking at requirements that have familiarity with the programming and searching for one that is very powerful. In QTP, users interact with applications using synchronized test scripts and an active screen. QTP also has an easy interface due to its GUI; however, there is a mode for experts to work with too. This makes QTP seem easy to use but it is also very powerful.

Software Testing Tools Winrunner

When it comes to the script recording modes, WinRunner is context sensitive and therefore uses a flat object hierarchy. Also WinRunner is analog and therefore captures any input inserted to it, be it keyboard input, a mouse path, or even a mouse click. QTP, on the other, uses a multi-level object hierarchy. Also, QTP is low-level and therefore only sues mouse coordinates.

WinRunner offers a programmatic representation when creating scripts. It uses TSL which is similar to C language. TSL is a procedural language and uses objects from a GUI map. QTP on the other hand creates scripts in two modes. One of these can be icon based while the other can be a programmatic representation. QTP uses VB script, which is an object-oriented language similar to VB. All the objects used come from the object repository.

Winrunner Software Testing Tool Free Download

In object storage and operations, WinRunner stores its content in a flat hierarchy and this can be viewed using a GUI spy. The content is also stored in a GUI Map. For any new objects, a temporary GUI Map is developed by WinRunner to hold new objects. QTP on the other hand uses a multilevel object hierarchy for storage of its content. Just as in WinRunner it can be viewed using an object spy and is stored in the object repository. Content is automatically stored in the object repository.

Other areas of difference include transaction measurement that is handled by TSL programming in WinRunner, while in QTP it is done by VBScript programming. Any data-driven operations create iterations automatically in WinRunner. QTP on the other hand creates iterations automatically and programmatically for any data-driven operations. Finally, WinRunner handles exceptions using the exception editor while QTP uses Rec.


WinRunner and QTP were developed by HP

WinRunner users interact with a focus on the test script

Winrunner Software Testing Tool

QTP users interact with applications using synchronized test scripts and active screens

Winrunner Software Testing Tool Free Download For Windows 7

Beetel router 450tc2 firmware download. WinRunner uses TSL while QTP uses VBScript

Winrunner Software Testing Tool

WinRunner in object storage operations stores the objects in a flat hierarchy while QTP stores objects in a multilevel hierarchy

  • The Difference Between Mediation and Conciliation - April 15, 2018
  • Difference Between the Jscripts and Java Scripts - November 17, 2013
  • Difference Between EJB 2.1 and EJB 3.0 - November 16, 2013