Winrunner Vs QTP (上集)

WinRunner Compared to QuickTest Pro
Environment Coverage Comparison:

Common environments shared by both WinRunner and QuickTest Pro:

QuickTest Pro Only Environments:

Feature Comparison:
Common features found in both WinRunner and QuickTest Pro:

WinRunner Only Environments:

QuickTest Pro Only Environments:

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 scrīpt 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 scrīpt.  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 VBscrīpt.
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 VBscrīpt 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.

            scrīpt 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 scrīpt – without having to navigate back to that location in your application like you have to with WinRunner.  This greatly speeds up scrīpt development.
QuickTest Pro currently has built in integration with WinRunner in order to be able to call existing scrīpts, which is great for customers who already have a large test scrīpt investment with WinRunner.  Likewise WinRunner 8.0 is to have the ability to also call QuickTest Pro scrīpts.  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 scrīpts 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 scrīpt development is quicker.  We really enjoy using QuickTest Pro and highly recommend it as the functional testing tool to use.

QuickTest Pro is our functional testing tool of choice!