很多初入行的朋友使用测试工具进行功能测试的时候,总是会遇到QTP和WinRunner的选择问题,为什么同样一家公司会出两个功能类似的工具哪? 下面是一篇关于这两个工具的对比介绍,其实从我自己的经验来看,WinRunner虽然推出较早,但是因为一些功能的缺陷,导致后期很难推广,而Quick Test Professinal(QTP)虽然没有师兄WinRunner出道早,然后内功深厚,所以很受欢迎,而且Mercury公司以后的主要发展策略是QTP,虽然文章中说并没有计划Phase out WR,但是已经不再出新版本了. 针对这两个工具的3年左右的使用经验,我的感受是WR比QTP的逊色的地方主要是几点:

1. WR的对象管理不如QTP那么有效

2. WR的语言主要是基于类C的TSL,是Mercury发明的语言,明显不如基于VBscrīpt的QTP强

3. WR的稳定性不行,而且无意人为的干扰可能导致回放的失败

4. WR对Java的支持也不如QTP那么强

WinRunner vs. QuickTest Pro

Quick Comparison

11

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:

<!--[if !supportLists]--> <!--[endif]-->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 (scrīpts/functions) from QuickTest Pro without any modification to these assets.

<!--[if !supportLists]--> <!--[endif]-->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.

<!--[if !supportLists]--> <!--[endif]-->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.

WinRunner Compared to QuickTest Pro

Environment Coverage Comparison:

<!--[if !supportLists]--> <!--[endif]-->Common environments shared by both WinRunner and QuickTest Pro:

<!--[if !supportLists]--> <!--[endif]-->WinRunner Only Environments:

<!--[if !supportLists]--> <!--[endif]-->QuickTest Pro Only Environments:

Feature Comparison:

<!--[if !supportLists]--> <!--[endif]-->Common features found in both WinRunner and QuickTest Pro:

<!--[if !supportLists]--> <!--[endif]-->WinRunner Only Environments:

<!--[if !supportLists]--> <!--[endif]-->QuickTest Pro Only Environments:

What We Recommend

QuickTest Pro is our functional testing tool of choice!

Most customers are in either of two situations:

<!--[if !supportLists]--> <!--[endif]-->Existing WinRunner customers asking “Should we switch to QuickTest Pro?”

<!--[if !supportLists]--> <!--[endif]-->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:

<!--[if !supportLists]--> <!--[endif]-->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.

<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->

<!--[if !supportLists]--> <!--[endif]-->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.

<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->

<!--[if !supportLists]--> <!--[endif]-->We feel that there are many more “point and click” features in QuickTest Pro than WinRunner. This makes its use easier.

<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->

<!--[if !supportLists]--> <!--[endif]-->All the same features found in WinRunner are found in QuickTest Pro plus more.

<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->

<!--[if !supportLists]--> <!--[endif]-->Data Table integration is much easier and simpler with QuickTest Pro.

<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->

<!--[if !supportLists]--> <!--[endif]-->Data Driven Testing is easier with more options in QuickTest Pro.

<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->

<!--[if !supportLists]--> <!--[endif]-->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.

<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->

<!--[if !supportLists]--> <!--[endif]-->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.

<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->

<!--[if !supportLists]--> <!--[endif]-->Parameterization is much easier in QuickTest Pro and basically anything in QuickTest Pro can be parameterized (statements, checkpoints and the Object Repository).

<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->

<!--[if !supportLists]--> <!--[endif]-->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.

<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->

<!--[if !supportLists]--> <!--[endif]-->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!

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 scrīpt to simulate the same actions just performed. The scrīpt 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.

Here is the descrīption from the Mercury “Features and Benefits” section of the WinRunner web page:

Significantly increase power and flexibility of tests without any programming: The Function Generator presents a quick and error-free way to design tests and enhance scrīpts without any programming knowledge. Testers can simply point at a GUI object, and WinRunner will examine it, determine its class and suggest an appropriate function to be used.

Use multiple verification types to ensure sound functionality: WinRunner provides checkpoints for text, GUI, bitmaps, URL links and the database, allowing testers to compare expected and actual outcomes and identify potential problems with numerous GUI objects and their functionality.

Verify data integrity in your back-end database: Built-in Database Verification confirms values stored in the database and ensures transaction accuracy and the data integrity of records that have been updated, deleted and added.

View, store and verify at a glance every attribute of tested objects: WinRunner’s GUI Spy automatically identifies, records and displays the properties of standard GUI objects, ActiveX controls, as well as Java objects and methods. This ensures that every object in the user interface is recognized by the scrīpt and can be tested.

Maintain tests and build reusable scrīpts: The GUI map provides a centralized object repository, allowing testers to verify and modify any tested object. These changes are then automatically propagated to all appropriate scrīpts, eliminating the need to build new scrīpts each time the application is modified.

Test multiple environments with a single application: WinRunner supports more than 30 environments, includin