Software Testing Social Network

Each Test case is built using a series of Quick Test Professional Functions. Each function executes Quick Test Professional code to input data onto a screen.
Each object in the Quick Test Professional Function resides in the Object Repository, thus allowing Quick Test Professional to identify all fields in the application.
•    Each test case uses functions. Each function is either an applet on a screen or a whole screen depending on the amount of fields.
•    Each function is named AUT_Screen Name e.g. MyApps_Close_Application
•    Every field/object on the screen or applet must be learnt into the object repository and renamed where required to a more meaningful screen name.
•    Each function library must reside as .vbs file
•    All functions are accessible via the step generator.

The following are pre-requisites or dependencies for QTP automation:

•    Knowledge and hands-on experience with the use of QTP;
•    Quality Centre (QC) and QTP installed and configured;
•    QC and QTP are integrated;
•    QTP Add-Ins are installed (if required);
•    QC user groups are defined and granted access to Quality Centre projects;
•    The application or product is in a stable state;
•    Creation of new automated scripts requires existing manual test cases to have been executed successfully.  This task is performed by the application tester or business representative and is performed prior to handover to QTP automation.
•    The manual test cases must have been executed successfully and that there are no other changes in the application.  Existing automated scripts can be updated directly to reflect the changes as part of maintenance releases.
•    All test cases must start and end at the same point. This is normally the First screen of the application. This allows for test cases to be batched together into a test suite.
•    All environment, software or data table changes must be advised to the automated testing team. There will potentially be an impact on the running of automated test cases with the introduction of these changes.
•    The test cases must not be data dependent.  All data required in the test case must be created in the test case. In the event that data cannot be created and the test case is data dependent, the data must be able to be restored, or manipulated back to the initial state after a test case updates the data. This then allows for any test case to be rerun at anytime


Existing manual test cases exist in QC in the standard format (see the QC user guide) and a copy of the test case to be automated are placed in the regression folder alongside any existing automated scripts. Refer to Section 6.1 for further information regarding Manual Test Cases.

QTP is a functional automated testing tools, and the page loading time or  response time of a web application should be a performance testing thing.But as a matter of fact, QTP can also get page load time statistics by some functions. Because QTP using a VBS script and VBS script is so powerful that it can call any windows of the COM components and objects. So the idea of getting page load time is very simple, that is, we want to use VBS for IE page and get statistics of the page load time.

Implementation steps:

1. Make sure the correct Add-in is loaded for the application under test. For example, if the procedure is to test the Java class, we must load the Java Add-in. Other commonly used Ad-ins for QTP are QuickTest Professional Oracle 6.5 Add-in, QuickTest Professiona Siebel 8.0 Add-in, and QuickTest Professional Terminal Emulator 8.0 Add-in. To get more details for each of the Add in please check the corresponding QTP_Install_Guide.pdf and Main_Users_Guide.pdf found.
2. Use QTP Virtual Objects feature for non recognized objects:
Using the Virtual Object Wizard, you can map a virtual object to a standard object class, specify the boundaries  and the parent of the virtual object, and assign it a name. You can also group your virtual objects logically by assigning them to collections. Goto Tools -> Virtual Objects -> New Virtual Object, there will be Virtual Object Wizard dialog box to add some support to the custom/wrapper class control set to a virtual control and then add it to the object library But  the virtual object is dependent on the coordinates so if the page is moved, it will not work.

3. Change the QTP's own means of identification of a control from the tools - Object Identification. It lists all of the QTP controls, as well as the how QTP identify those controls. You can give it to add X, Y coordinates for recognition.  This change can solve some of the problems.

4. The use of low-level recording or mouse recording. With the LowLevelRecording/AnlogRecording you can record the coordinate of the screen to achieve the result. But this is poor for maintenance.

[Method 1]: the use of "SystemUtil.Run" command to support any file format called For example: SystemUtil.Run "C: testfile.txt"
[Method 2]: Use "InvokeApplication" command (invoke the executable program) Call executable applications such as: InvokeApplication "C: Program Files Plus! Microsoft Internet IEXPLORE.EXE"
[Method 3]: The "Excutefile" function calls the external file has three kinds of file formats can be called, and they are *. sql; *. vbs; *. txt suffix three kinds of documents such as: ExecuteFile "C: TEST.VBS"
Note: ExecuteFile function Although it can be used to import an external file into the QTP script, but can not be shared between the various ACTION. If you want it to be shared between the various ACTION external file, please refer to the following cases
[Method 4]: in [resources] option is called an external file in the "resource" option, there are three kinds of file formats which can be called, and they are *. sql; *. vbs; *. txt files of three suffix . Test → Settings → Resources → + Resources by adding an external file, you can in a QTP script to be shared between all of the external file ACTION