? Ease of use.

? Simple interface.

? Presents the test case as a business workflow to the

tester (simpler to understand).

? Uses a real programming language (Microsoft?sVBScript)

with numerous resources

available.

? QuickTest Pro is significantly easier for a non-technical

person to adapt to and create

working test cases, compared to WinRunner.

? Data table integration better and easier to use than

WinRunner.

? Test Run Iterations/Data driving a test is easier

and better implement with QuickTest.

? Parameterization easier than WinRunner.

? Can enhance existing QuickTest scripts without

the ?Application Under Test? being

available; by using the ActiveScreen.

? Can create and implement the Microsoft Object Model

(Outlook objects, ADO objects,

FileSystem objects, supports DOM, WSH, etc.).

? Better object identification mechanism.

? Numerous existing functions available for implementation ?

both from within QuickTest Pro

and VBScript.

? QTP supports .NET development environment (currently

WinRunner 7.5 does not).

? XML support (currently WinRunner 7.5 does not).

? The Test Report is more robust in QuickTest

compared to WinRunner.

? Integrates with TestDirector and WinRunner (can kick off

WinRunner scripts from

QuickTest).

Cons:

? Currently there are fewer resources (consultants and

expertise) available due to QTP being a

newer product on the market and because there is a

greater Demand than Supply, thus fewer

employee/consulting resources.

? Must know VBScript in order to program at all.

? Must be able to program in VBScript in order to implement

the real advance testing tasks

and to handle very dynamic situations.

? Need training to implement properly.

? The Object Repository (OR) and ?testing environment?

(paths, folders, function libraries, OR) can be difficult

to understand and implement initially.