Quick Test Professional (QTP)

During replay, the script will then be replayed like a Windows VB Script, launching the windows and activating the buttons as what is being recorded.  A sound knowledge of VB script is actually helpful in maintaining the scripts however not necessarily needed as QTP is relatively easy to use.  A tip here is you can actually use VB script in Windows to run automation without even using QTP.  It works the same way but a little low-level work is required and you need to understand the various ways the windows and objects are called in the Windows environment.

In QTP, you can add check points to determine if your application response as intended.  You can also use output values similar to the concept of correlation in QTP to handle dynamic data.  The output values are also used to be input values for the next step depending on how the test case is designed.

As for the licenses, they worked in two ways.  Either you use a Seat license or a Concurrent license.  The seat license is tied to the machine that installed the license while the concurrent license requires a license server to be available for it to retrieve the license information.  The license will decide the type of application you can record; generally called an Add-In.  QTP has various Add-In to suit the needs of the customer.  The common one is Web, Java script and ActiveX.  Other supported technologies that require an Add-In are Java, Oracle, SAP, etc.

Of all the virtues of using QTP, you will still need to be careful on the following and use it correctly:

• Resolution of the recording machine and replay machine MUST be the same – QTP rely on the resolution of the machines to recognize the coordinates and size of the objects.  Problem will arise when the resolution of the recording machine and replay machine is different.  Example, the script was recorded in 1024 x 768 resolution while it was replayed in a 1280 x 800 resolution may result in the script generating error as the objects have changed their coordinates.
• Iteration of the script requires the start and end point to be the same – For a script to iterate successfully, the script should be recorded in a way that the start and end point are the same.  Example, the script starts off with the login page and proceeds with login and some activities then logout to return to the login page.  In this manner, the script will be able to iterate with the next set of value such as a new login account.
• Context-sensitive – Context sensitive menus may require the use of Object Spy feature in QTP.  Context sensitive menu such as mouse-over menu that will show the sub-menu.  This will require pressing “Crtl-Key” when using the Object Spy and inserting the action (and object) into the script.  However, we recommend recording in a lower granularity (in analog) to capture as much objects as you can before proceeding to use the Object Spy.
• Preparation of initial test data – Most often people ignored the need for a baseline set of data for testing.  After each functional (regression) test, the data needs to be refreshed to a clean set before the script can work again.
• Still dependent on a well-designed test case – To make the tool really useful, the tool still highly depends on a well-designed test case.  Without a well designed test case, the downstream activities such as recording and modifying may not serve its purpose well.

The information should give you an overview of how QTP works and what you should take note after purchase (or even before purchase).  We hope that it will be useful to you and do share with us on anything related to QTP.