QuickTest or WinRunner Essay Example | Topics and Well Written Essays - 1250 words

QuickTest or WinRunner - Essay ExampleMercury QuickTest professional person (QTP) and WinRunner (WR) ar automated functional Graphical User Interface (GUI) stressing woodpeckers make believed by the HP quality counseling and performance testing resolutions subsidiary Mercury Interactive (now HP Software) found in Sunnyvale, CA, with R&D in Israel (Mar, 2007, p. 2) that allow the automation of user actions on a web or client based computer application. WinRunner was introduced in 1995 while QuickTest Pro has been available since about 2002 (LoPorto, n. d., p. 3).The Software Test & Performance 2006, examiners Choice Grand Award winner (Award-Winning QA by Any Other Name Would notion as Sweet, 2007, para.1), Mercury QuickTest Professional is a next-generation automated testing solution. It provides the industrys best solution for functional test and regression test automation addressing every major computer software application and environs including next-generation develop ment technologies such as Web Services, Macromedia Flex, .NET, J2EE, and ERP/CRM applications (Mercury Functional Testing Mercury QuickTest Professional , 2006, p.2). Mercury QuickTest Professional uses the Keyword-driven testing concept to radically simplify test creation and maintenance. Its unique Keyword-driven testing approach enables the test automation experts to cede full access to the underlying test and intent properties, via an integrated scripting and debugging environment that is round-trip synchronised with the Keyword View (Mercury QuickTest Professional, 2007, para. 2).... d., p. 3).Over the past decade, WinRunner is one of the market leaders when it comes to automated functional testing tools. WinRunner utilizes a Graphical User Interface (GIU) Map approach to create an automated test script. Since each object within a test has a minimum set of physical attributes that make it unique (Korhonen, 2000, p. 26) whence WinRunner recognizes objects like buttons and ed it fields by their unique properties.It can also be used to create automated scripts for applications created using a range of technologies, including Java, Siebel, PowerBuilder, and Delphi (Mercury WinRunner, 2006, p. 2). It has gain an enormous popularity and thousands of developers has gathered under its flag who have improved their skills in this product over the years of their professional careers. With Mercury WinRunner, the organization reduces testing time by automating repetitive tasks, optimizes testing efforts by covering diverse environments with a single testing tool and maximizes return on investment through modifying and reusing test scripts as the application evolves (Quality Assurance, n. d., pp. 1-3). Although WinRunner has proved to be an economical testing tool and it has become an industry standard as functional testing technology, yet continuous technological development scenario has highlighted its few short comes or limitations over its applications. In a n umber of applications, WinRunner has locomote short to recognize a lot of texts, graphics and drop-down lists hence failed to make sure that all of the companys software 100% error-free. To be able to check all of the texts, graphics and drop-down lists, developers have to do more work. This actually degrades the automation testers efficiency and makes it impossible for