Test Partner versus Quicktest Pro
We are eveluating Test Partner and Quicktest Pro for our organization.
We intend to test our Dot Net based applications for the time being.
So can anyone of you please tell similarities and differrences between these two tools?
Thanking in Anticipation
Re: Test Partner versus Quicktest Pro
I did a review myself and found the following facts.
Can anyone review them and verify them?
Some of the similarities between both the QuickTest(QTP) and Test Partner(TP) are
• Both support Data Driven Tests.
• Both support checking for any given aspect at any point of time using CheckPoints(For QTP) And Checks(For TP).
• Error handling i.e invoking any predefined set of actions, when particular error occurs using Recovery Scenario manager
(For QTP) and events-Whenever(For TP)
• Identifying properties of different objects by using Object Spy(For QTP) and Identify or Com Spy(For TP)
• Both support mapping of non-standard objects to be mapped to standard objects by using Virtual Objects (For QTP) And Alias
• Both support debugging using Breakpoints.
• One can view the Pass/Fail status using Test Results(For QTP) And Logs(For TP).
• Strong Object-level Testing and Configuration - Both provide users an extensive number of properties associated with
controls, and allows them to pre-configure which ones to learn/ignore during record.
• Both support two modes of recording- one mode refers to Object repository or Object map while in other Descriptive
Programming is used i.e. control properties are explicitly mentioned in the statements.
Differences are :--
• Asset Versioning is available in Test Partner.
• Data Test Creation is much easier in QTP.
• TP has support for Modular Scripting (Functions).
• TP is good for more than one testers working on same project due to sharing of database.
• QTP shows you screen corresponding to each statement in your script, by highlighting the object if the cursor is on a object
name, making it easier to recognize which object you are working on.
• using QTP 8 you can store your results build wise, without needing any Test management Tool, because results are stored as
• The concept of a database to store test assets in TP allows for more flexibility in asset re-use than does the file storage
system that is used by the mercury tools.
• TestPartner's scripting language (VBA) is more powerful and flexible than QTP's (VBS).
• The most annoying problem with QTP is that recorded tests became unstable and could not be relied on to playback correctly.
In TP i found that a test recorded would playback without error days, weeks and even months later.