Professional Documents
Culture Documents
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.
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’s prime 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.
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
Recommend
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.
• 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.
• 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.
• 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.
Winrunner
Summary
This product is a mature tool that has been around since approximately 1995. It
interfaces with most of the leading development toolkits using the WindowsAPI and
toolkit DLLs to interface with the “Application Under Test”.
WinRunner offers a recording feature that will watch the individual tester and generate a
test script to simulate the same actions just performed. The script is displayed as a
program which can be enhanced with checkpoints, logic and special
coding/programming.
WinRunner also has integration with Excel spreadsheets for data driven testing and the
ability to write data out in Excel format or in simple text files.
Pros
Cons
Here is the description from the Mercury Interactive “How it Works” section of the
QuickTest Pro web page:
You can then enter test data into the Data Table, an integrated spreadsheet with the full
functionality of Excel, to manipulate data sets and create multiple test iterations, without
programming, to expand test case coverage. Data can be typed in or imported from
databases, spreadsheets, or text files.
Advanced testers can view and edit their test scripts in the Expert View, which reveals
the underlying industry-standard VBScript that QuickTest Professional automatically
generates. Any changes made in the Expert View are automatically synchronized with
the Keyword View.
Once a tester has run a script, a TestFusion report displays all aspects of the test run: a
high-level results overview, an expandable Tree View of the test script specifying exactly
where application failures occurred, the test data used, application screen shots for
every step that highlight any discrepancies, and detailed explanations of each checkpoint
pass and failure. By combining TestFusion reports with Mercury Quality Management,
you can share reports across an entire QA and development team.
QuickTest Professional also facilitates the update process. As an application under test
changes, such as when a “Login” button is renamed “Sign In,” you can make one update
to the Shared Object Repository, and the update will propagate to all scripts that
reference this object. You can publish test scripts to Mercury Quality Management,
enabling other QA team members to reuse your test scripts, eliminating duplicative
work.
quicktest-professional_works
We like QuickTest Pro and now prefer implementing it over WinRunner. When you get
into advance testing scenarios, QuickTest Pro has more options and they are easier to
implement compared to WinRunner in our opinion.
Do to the similarities in concept and features, an experienced WinRunner user can easily
convert to QuickTest Pro and quickly become an efficient Test Automation Engineer!
We recommend that existing customers begin all new development with QuickTest Pro
and use the built-in feature of calling WinRunner scripts from QuickTest Pro for all
existing WinRunner scripts that they already have. As older scripts require updates and
time permits, we recommend replacing them with QuickTest Pro scripts. Eventually you
will be able to convert your test script library with all QuickTest Pro scripts.
Pros
• Will be getting the initial focus on development of all new features and
supported technologies.
• Ease of use.
• Simple interface.
• Presents the test case as a business workflow to the tester (simpler to
understand).
• Numerous features.
• Uses a real programming language (Microsoft’s VBScript) 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