- What is loadrunner and winrunner pro#
- What is loadrunner and winrunner plus#
- What is loadrunner and winrunner windows#
What is loadrunner and winrunner pro#
This eases the transition from WinRunner to QuickTest Pro for existing customers. Likewise WinRunner 8.0 is to have the ability to also call QuickTest Pro scripts. 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. This greatly speeds up script development. 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.
What is loadrunner and winrunner windows#
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.
What is loadrunner and winrunner plus#
This makes its use easier.Īll the same features found in WinRunner are found in QuickTest Pro plus more.ĭata Table integration is much easier and simpler with QuickTest Pro.ĭata Driven Testing is easier with more options in QuickTest Pro. We feel that there are many more “point and click” features in QuickTest Pro than WinRunner. QuickTest Pro use the Microsoft programming language VBScript which is very powerful, has lots of capabilities and there are lots of resources available. These types of languages can be very restrictive and you are limited on available resources. WinRunner uses TSL which is a proprietary language of Mercury. 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. This is very easy to get used to and non-technical people adapt to it quicker and feel more comfortable working with it. However QuickTest Pro offers a “Tree View” which is an icon-based view of the script. For testers who do not have a technical background, they are not always comfortable with having to always look at code. It is based on the “C” programming language and therefore looks very similar. TSL is the WinRunner programming language developed by Mercury. The WinRunner interface forces the user to look directly at TSL code. QTP also offers many features not found in WinRunner that make test script creation, enhancement and maintenance easier. QTP offers many features that are found in WinRunner, but are easier to use. Overall, QuickTest Pro is easier to use and implement for both technical and non-technical testers in comparison to WinRunner. 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. 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. So like many existing WinRunner customers we have a huge knowledge investment in WinRunner ourselves. We have been implementing WinRunner since the very first version of it.
We have been implementing Mercury’s products since 1992 and have senior level expertise in WinRunner. New customers asking “Which should we get, WinRunner or QuickTest Pro?” Most customers are in either of two situations:Įxisting WinRunner customers asking “Should we switch to QuickTest Pro?” QuickTest Pro is our functional testing tool of choice! Shared Object Repository Rapid Object Importįunction Generator*(coming in v7.0) Run Wizard*(coming in v7.0) Operating Systems Windows 98, 2000, NT, ME, XPĬommon features found in both WinRunner and QuickTest Pro:
Web-Related Environments IE, Netscape, AOL I think this is sufficient for u to understand clearly.Ĭommon environments shared by both WinRunner and QuickTest Pro:
0 kommentar(er)
