QTP Recording Modes

Recording and Running

It is a Process of Recording user operations on AUT (Application Under Test). During Recording QTP Creates steps in Keyword view, and generates them in a script in the Expert view. Simultaneously it adds Objects information into Object Repository.

Normal Recording:
We choose normal recording mode by default. If we need to capture the objects in object repository, and the events on the objects will be captured in test script.

After the normal mode of recording, different files will be generated at the test script and action level.

After recording and saving the test script a folder will be created with the script name.

The files generated at the test script are:

1) default.cfg - Configuration file
2) default.usp - Run logic file
3) default.xls - Data file, which contains Global and Action1 sheet
4) Parameters.mtr - Test script parameters
5) Test2.usr - Test script main file
6) Action0 folder - Contains the script settings to load the supportive actions and actions sequence scripts
7) Action1 folder - Contains actual action scripts which can be executable

The files generated at action level are:
1) script.mts - Test script
2) Resource.mtr - Action parameters
3) ObjectRepository.bdb - Object repository
4) Snap Shots folder - Contains all the step level snapshots

Analog Recording:
Analog Recording will be chosen, when the mouse drags and keyboard events needs to be captured in the test. We need to switch from normal to analog. We cannot directly start recording in Analog.

Example: if you want to capture the digital signature or file movements we choose analog recording type.

The additional file generated is - AnalogTrackList.dat.

All the mouse movements and key board events will be captured in the .dat file.

Low level recording:
We choose low level recording, when the low level events on the objects needs to be captured. If you want to capture the pixel position level operations relative to object, we choose low level recording.

 example: An image is having some of the portion as link and other area is as static element. If you want to click on the link area of the image, we switch from normal to low level to capture the position level click operations on the object.

The basic differences :

Normal Recording	Analog Recordings	Low Level Recording
This is the default mode of recording	Need to be switched from normal record in	Need to be switched from normal recording
Objects will be captured in the object repository at context level	Mouse events and keyboard events will be captured	Low level operations on the objects will be captured. These are the generic objects captured in repository
Each operation will be captured as a step in the test script	All the operations will be captured in a seperate .dat file	Each operation will be captured as a step at the low level in the test script

Why qtp is not recording the events on windows based application by default :

The default record and run time settings are set to "record and run only on" radio button and "applications opened by Quick test." check box

That means, q t p recognizes the objects on the application which is opened by QTP. If we manually open the application and record the events, q t p will not capture the events.

To record the application events on already opened application we need to choose the radio button "Record and run test on any open Windows-based application"

Which case do you choose record and run test on any open windows based application?

The record and run test on any open windows based application is chosen, whenever the recording needs to be done on any opened application.

For example:
1) Whenever any dependence test case needs to be automated
2) If the application needs to be captured from the mid of the test case
3) If the test steps needs to be added to the existing test case
4) Whenever the application invocation not necessary to be part of recording

When do you choose record and run only on applications opened by q t p?

Record and run only on applications opened by q t p  is chosen, whenever the application invocation needs to be part of the recording.

The advantages of using this option is:
1) Only application events will be captured as part of recording. Other application events will not be captured as part of recording. For example, during recording if you are chatting on Google talk and poking on face book, those events will not be captured as part of recording.
2) If you want to achieve the test cases independence, we choose this option

How do you set the record time settings for newly installed add INS in q t p?

The record time settings for newly installed add ins can be set by following steps:

1)    Open QTP
2) Select Automation->Record and Run Settings menu options
3) Select the tab related to the newly installed add-in
For example, after the installation of java add-in, java add-in settings is visible on "Record and Run Settings"
4) Give the record and run time settings related to the new add-in

Where are the objects captured during the recording in q t p?

The objects will be captured in local object repository during recording in q t p.

For each interaction with an application object, the object will be captured in object repository. The action on the object will be captured as method in the test script.