Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
8Activity
0 of .
Results for:
No results containing your search query
P. 1
QTP_Vs_WinRunner

QTP_Vs_WinRunner

Ratings: (0)|Views: 311|Likes:
WinRunner vs. QuickTest Pro
WinRunner vs. QuickTest Pro

More info:

Published by: RamaDurgarao Peddireddy on Jul 11, 2009
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

05/11/2014

pdf

text

original

 
WinRunner vs. QuickTest Pro
Overview
Today Mercury has two functional testing tools – WinRunner (WR) and QuickTestProfessional (QTP). WinRunner has been around since about 1995 while QuickTest Prohas been available since about 2002. We have lots of companies asking us “What’s thedifference between WinRunner and QuickTest Pro?” and “If they are both functionaltesting tools from the same company, then which one of the tools should we use?” Thisdocument was developed as a short simple reference in helping to understand the basicsabout the tools in order to answer these two questions.Mercury’s position on the two tools is this:The strategic direction for Mercury and its customers for Functional Testing is productintegration. The new releases of QTP and WR improve already existing integration wherecustomers can leverage complete WinRunner assets (scripts/functions) from QuickTestPro without any modification to these assets.QuickTest Pro 8 has recently been released and WinRunner version 8.0 is planned forNovember 2004. There are no plans to phase out WinRunner.QuickTest Pro remains Mercury’s prime product for best customer satisfaction andexperience. For customers who need both products, Mercury continues to offer MercuryFunctional Testing as a combined package of both product offerings. The BusinessProcess Testing system will be extended to incorporate components designed inWinRunner for the WinRunner 8.0 release in November.
Environment Coverage Comparison
•1
Common environments shared by both WinRunner and QuickTest Pro:Web-Related EnvironmentsIE, Netscape, AOLJDK, Java Foundation Classes, AWTSymantec Visual CaféActiveX ControlsERP/CRMOracle: Jinitiator, 11i, NCACustom Client ServerWindowsC++/CVisual BasicOperating SystemsWindows 98, 2000, NT, ME, XPLegacy3270, 5250 EmulatorsVT100
•2
WinRunner Only Environments:Custom Client/ServerPowerBuilderForteDelphiCenturaStingraySmallTalkERP/CRMBaanPeopleSoft WindowsSiebel 5, 6 GUI ClientsOracle GUI Forms 
•3
QuickTest Pro Only Environments:Source: Automated Solutions, IncPage 1 of 6
 
WinRunner vs. QuickTest Pro
ERP/CRMSAPSiebel 7.xPeopleSoft 8.x.NetWinFormsWebForms.Net controlsWeb ServicesXML, HTTPWSDL, SOAPJ2EE, .NetMultimediaRealAudio/VideoFlash
Recommend
We have been implementing Mercury’s products since 1992 and have senior levelexpertise in WinRunner. We have been implementing WinRunner since the very firstversion of it. So like many existing WinRunner customers we have a huge knowledgeinvestment in WinRunner ourselves. However we have worked on the Mercurydevelopment team on the QuickTest Pro 6.0 and 6.5 releases, and have solid real-world experience in implementing QuickTest Pro since the 6.0 release. We havefound it to be a great tool to use and recommend it to all customers! Overall, werecommend using QuickTest Pro unless for some reason you have to use WinRunnerdue to an unsupported environment not existing in QuickTest Pro.Overall, QuickTest Pro is easier to use and implement for both technical and non-technical testers in comparison to WinRunner. QTP offers many features that arefound in WinRunner, but are easier to use. QTP also offers many features not foundin WinRunner that make test script creation, enhancement and maintenance easier.Let’s quickly discuss some key issues:
The WinRunner interface forces the user to look directly at TSL code. TSL isthe WinRunner programming language developed by Mercury. It is based onthe “C” programming language and therefore looks very similar. For testerswho do not have a technical background, they are not always comfortablewith having to always look at code. However QuickTest Pro offers a “TreeView” which is an icon-based view of the script. This is very easy to get usedto and non-technical people adapt to it quicker and feel more comfortableworking with it. For the technical user, they can always switch over to the “Expert View” in QuickTest and look directly at code, and program away usingVBScript.
WinRunner uses TSL which is a proprietary language of Mercury. These typesof languages can be very restrictive and you are limited on availableresources. QuickTest Pro use the Microsoft programming language VBScriptwhich is very powerful, has lots of capabilities and there are lots of resourcesavailable.
We feel that there are many more “point and click” features in QuickTest Prothan WinRunner. This makes its use easier.Source: Automated Solutions, IncPage 2 of 6
 
WinRunner vs. QuickTest Pro
All the same features found in WinRunner are found in QuickTest Pro plusmore.
Data Table integration is much easier and simpler with QuickTest Pro.
Data Driven Testing is easier with more options in QuickTest Pro.
Script enhancements are typically easier with QuickTest Pro because it has theActive Screen where the windows and objects in your application are capturedfor later use. Using a “point and click” capability you can easily interface withobjects, their definitions and create checkpoints after having recorded a script– without having to navigate back to that location in your application like youhave to with WinRunner. This greatly speeds up script development.
QuickTest Pro currently has built in integration with WinRunner in order to beable to call existing scripts, which is great for customers who already have alarge test script investment with WinRunner. Likewise WinRunner 8.0 is tohave the ability to also call QuickTest Pro scripts. This eases the transitionfrom WinRunner to QuickTest Pro for existing customers.
Parameterization is much easier in QuickTest Pro and basically anything inQuickTest Pro can be parameterized (statements, checkpoints and the ObjectRepository).
Capturing various output values is easier and simpler with QuickTest Pro.Using this capability with parameterization enables you to easily developscripts that can do more in regards to testing.
We have been implementing QuickTest Pro in real-world environments andhave found it much easier to use, advance features are easier to implementand the script development is quicker. We really enjoy using QuickTest Proand highly recommend it as the functional testing tool to use.
Winrunner
Summary
This product is a mature tool that has been around since approximately 1995. Itinterfaces with most of the leading development toolkits using the WindowsAPI andtoolkit DLLs to interface with the “Application Under Test”.WinRunner offers a recording feature that will watch the individual tester and generate atest script to simulate the same actions just performed. The script is displayed as aprogram which can be enhanced with checkpoints, logic and specialcoding/programming.WinRunner also has integration with Excel spreadsheets for data driven testing and theability to write data out in Excel format or in simple text files.- WinRunner “Features and Benefits” webpage from Mercury:Winrunner features Source: Automated Solutions, IncPage 3 of 6

Activity (8)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
ravi_chandra_92 liked this
Rocket4 liked this
akbisoi1 liked this
pompipi123 liked this
yah_auto liked this
qa_nitin liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->