1. These notes on the software functionality automated test tool WinRunner from Mercury Interactive focuses on the hardest won (but easily forgotten) insights not.
2. Online Guide Books Books Online Online ® W inRunner 7. 0 Find T utorial Find Again Help T op of Chapter Back T a ble of Con t en t s 0 Books Books T a bl e o f C o nt en t s Online.

1. Winrunner Download

That's unprofessional and useless. The questioner needs a tutorial. The only place to get it is with the product itself. And while we are on the subject of prefessionalism, texting ('u' instead of 'you') is appropriate for 13-year-olds in a chat room but not for this forum.

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.

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.

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

Winrunner Download

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]

Helping Guides[edit]

Open Source Frameworks for WinRunner[edit]

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

See also[edit]

External links[edit]

References[edit]

1. ^FYICenter.com: '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.