Advantages of QTP over Winrunner

Why should anyone opt for QTP over Winrunner?

Prefer qtp. I think this is sufficient for u to understand clearly. Winrunner compared to quicktest pro environment coverage comparison: common environments shared by both winrunner and quicktest pro: web-related environments ie, netscape, aol jdk, java foundation classes, awt symantec visual café activex controls erp/crm oracle: jinitiator, 11i, nca custom client server windows c++/c visual basic operating systems windows 98, 2000, nt, me, xp legacy 3270, 5250 emulators vt100 winrunner only environments: custom client/server powerbuilder forte delphi centura stingray smalltalk erp/crm baan peoplesoft windows siebel 5, 6 gui clients oracle gui forms quicktest pro only environments: 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 feature comparison: common features found in both winrunner and quicktest pro: record/replay odbc & excel connectivity code editor & debugger recovery manager shared object repository rapid object import numerous checkpoints analog script & function libraries winrunner only environments: function generator database integration run wizard tsl mdi quicktest pro only environments: activescreen testguard tree view scriptfusion data table vbscript function generator*(coming in v7.0) run wizard*(coming in v7.0) 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 script 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 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. 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 vbscript 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. 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. Quicktest pro currently has built in integration with winrunner in order to be able to call existing scripts, which is great for customers who already have a large test script investment with winrunner. Likewise winrunner 8.0 is to have the ability to also call quicktest pro scripts. 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 scripts 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 script development is quicker. We really enjoy using quicktest pro and highly recommend it as the functional testing tool to use.

Hi Tina,

On the face of it, QTP is much more user-friendly tool which is much more adaptable working with Web-based applications and also provides an inbuilt Keyword-view enabling easy scripting for end user.

[U]A few distinct advantages QTP offers over WR. [/U]

[LIST][*]QTP is more user friendly and does not expose the end user to direct TSL coding. Inexperienced / non-technical people can use the keyword view toi better understand the script.
[*]An inbuilt Recovery Mechanism to handle various exceptions and application crashes etc.
[*]Ability to work in advanced manner with Object Repository in terms of Merge Tool, Object Repository Comparison, Exporting Local objects etc.
[*]Better Suport for VB, Java based applications due to inbuilt add ins.
[*]Easy intergration of external function files in terms of creating Libraries. Associated using Resources.
[*]Ability to spilt a single test into various actions making debugging easier and enabling better maintainability.
[*]Ability to set up Property Recognition Order and Prioritzation using Object Identification menu.[/LIST]

There would be many more which could be listed.

Cheers...

Does QTP have the ability to run multiple scripts in a row.
I need to run my QTP scripts to cover different scenarios and run them one by one with out manual interaction.

hai friend,

[Quote]Does QTP have the ability to run multiple scripts in a row.[/Quote]

Will you please explain this.

Thanks
Deepa

Hi,

Incase what you meant by "running multiple tests in a row" is equivalent to running QTP scripts ina flow or in a batch manner, there are 2 options -

Create a Driver script and use the Call <TestName> in a sequential manner. Ensure that all tests that need to be called exists within the same folder else you would have to specify the relative path for each test.

You also have an option under Tools - TestBatchRunner which is basically an inbuilt option provided to create Batch Tests. Invoke this option and specify the tests you wish to run. All selected tests would be run one after another without any interaction required.

NOTE : To enable Batch running or execute multiple scripts without Human Intervention, ensure each individual script is stable without any errors. Also ensure no script has an Input Prompts which requires the script to wait for User Input.

Cheers,