Quality Assurance and Testing: Winrunner Vs QTP
 

Winrunner

QTP Professional

Winrunner Vs QTP

WinRunner vs. QuickTest  Pro overview

Today Mercury has two functional testing tools – WinRunner (WR) and QuickTest Professional (QTP).WinRunner has been around since about 1995 while QuickTest Pro has been available since about 2002.We have lots of companies asking us “What’s the difference between WinRunner and QuickTest Pro?” and “If they are both functional testing tools from the same company, then which one of the tools should we use?”This document was developed as a short simple reference in helping to understand the basics about 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 product integration.  The new releases of QTP and WR improve already existing integration where customers can leverage complete WinRunner assets (scripts/functions) from QuickTest Pro without any modification to these assets.

·*QuickTest Pro 8 has recently been released and WinRunner version 8.0 is planned for November 2004.  There are no plans to phase out WinRunner.

·*QuickTest Pro remains Mercury’sprime product for best customer satisfaction and experience.  For customers who need both products, Mercury continues to offer Mercury Functional Testing as a combined package of both product offerings.  The Business Process Testing system will be extended to incorporate components designed in WinRunner for the WinRunner 8.0 release in November.


WinRunner Compared to QuickTest Pro

Environment Coverage Comparison:

·*Common environments shared by both WinRunner and Quick Test Pro:

Web-Related Environments

IE, Netscape, AOL

JDK, Java Foundation Classes, AWT

Symantec Visual Café

ActiveX Controls

ERP/CRM

Oracle: Jinitiator, 11i, NCA

Custom Client Server

Windows

C++/C

Visual Basic

Operating Systems

Windows 98, 2000, NT, ME, XP

Legacy

3270, 5250 Emulators

VT100

·*WinRunner Only Environments:

Custom Client/Server

PowerBuilder

Forte

Delphi

Centura

Stingray

SmallTalk

ERP/CRM

Baan

PeopleSoft Windows

Siebel 5, 6 GUI Clients

Oracle GUI Forms

·*Quick Test Pro Only Environments:

ERP/CRM

SAP

Siebel 7.x

PeopleSoft 8.x

.Net

WinForms

WebForms

.Net controls

Web Services

XML, HTTP

WSDL, SOAP

J2EE, .Net

Multimedia

RealAudio/Video

Flash

Feature Comparison:

·Common features found in both WinRunner and Quick Test Pro:

Record/Replay

ODBC & Excel Connectivity

Code Editor & Debugger

Recovery Manager

Shared Object Repository

Rapid Object Import

Numerous Checkpoints

Analog

Script & Function Libraries

·*WinRunner Only Environments:

Function Generator

Database Integration

Run Wizard

TSL

MDI

·*Quick Test Pro Only Environments:

ActiveScreen

TestGuard

Tree View

ScriptFusion

Data Table

VBScript

Function Generator*

(coming in v7.0)

Run Wizard*

(coming in v7.0)

What We Recommend

QuickTest Pro is our functional testing tool of choice!

Most customers are in either of two situations:

·*Existing WinRunner customers asking “Should we switch to QuickTest Pro?”

·*New customers asking “Which should we get, WinRunner or QuickTest Pro?”

We have been implementing Mercury’s products since 1992 and have senior level expertise in WinRunner.We have been implementing WinRunner since the very first version of it.So like many existing WinRunner customers we have a huge knowledge investment in WinRunner ourselves.However we have worked on the Mercury development 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 have found it to be a great tool to use and recommend it to all customers!Overall, we recommend using QuickTest Pro unless for some reason you have to use WinRunner due 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 are found in WinRunner, but are easier to use.QTP also offers many features not found in 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 is the WinRunner programming language developed by Mercury.It is based on the “C” programming language and therefore looks very similar.For testers who do not have a technical background, they are not always comfortable with having to always look at code.However QuickTest Pro offers a “Tree View” which is an icon-based view of the script.This is very easy to get used to and non-technical people adapt to it quicker and feel more comfortable working 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 using VBScript.

·WinRunner uses TSL which is a proprietary language of Mercury.These types of languages can be very restrictive and you are limited on available resources.QuickTest Pro use the Microsoft programming language VBScript which is very powerful, has lots of capabilities and there are lots of resources available.

·We feel that there are many more “point and click” features in QuickTest Pro than WinRunner.This makes its use easier.

·All the same features found in WinRunner are found in QuickTest Pro plus more.

·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 the Active Screen where the windows and objects in your application are captured for later use.Using a“point and click” capability you can easily interface with objects, their definitions and create checkpoints after having recorded a script – without having to navigate back to that location in your application like you have to with WinRunner.This greatly speeds up script development.

·*QuickTest Pro currently has built in integration with WinRunner in order to be able to call existing scripts, which is great for customers who already have a large test script investment with WinRunner.Likewise WinRunner 8.0 is to have the ability to also call QuickTest Pro scripts.This eases the transition from WinRunner to QuickTest Pro for existing customers.

·*Parameterization is much easier in QuickTest Pro and basically anything in QuickTest Pro can be parameterized (statements, checkpoints and the Object Repository).

·*Capturing various output values is easier and simpler with QuickTest Pro.Using this capability with parameterization enables you to easily develop scripts that can do more in regards to testing.

·*We have been implementing QuickTest Pro in real-world environments and have found it much easier to use, advance features are easier to implement and the script development is quicker.We really enjoy using QuickTest Pro and highly recommend it as the functional testing tool to use.