Recording in QTP

It is a process of recording user operations on AUT (Application Under Test). Recording is something which records all the user actions (like clicking a button, clicking a link, entering data, closing browser etc. We mostly capture expected results during recording. During Recording QTP creates steps in Keyword view, and generates them in a script in the Expert view. Simultaneously it adds Objects information into an Object Repository.

QTP supports 3 types of recording:

1. Normal Recording
2. Analog Recording
3. Low Level Recording

1. It recognize the objects in AUT regardless of their location on the screen
2. The Normal recording mode records the objects in your application and the operations performed on them.
3. This is default recording method.
4. In this Object Information will be stored in the object repository.

1. In Analog Mode recording, all the user actions will be recorded based on X, Y co-ordinates on the screen. Similarly typing text inside any of the controls also will be captured using X, Y co-ordinates with the action asset text.
   
2. This mode is useful for the operation which you can record at object level,such as drawing a picture,recording signature.
3. There are two types of recording in Analog: Record Relative to screen: In this QTP records User operations with respect to Desktop co-ordinates.Relative to window:In this QTP  records with respect to the window co-ordinates.
4. It can't record object information.
5. Analog recording require more disk space than normal recording mode.

1. All user actions are recorded in an object-oriented manner. For instance, no matter how you select a menu item (mouse click, shortcut, <Alt> and arrow), the generated code is the same: a ChooseMenu function is recorded. Within some applications, this intelligent recording does not work correctly. When Lowlevel Recording is selected, WinTask records keyboard and mouse actions exactly as they are performed.
2. This is a Special recording mode provided by the QTP which is used for recording at least some minimum operations on the Non-Supported Environments also.
3. We use this recording to record basic operations when QTP fails to identify a respective class
4. It is possible to edit the scripts after recording within QTP.
5. This mode records at the object level and records all runtime objects as window or window object Test objects.
6. Supports the following methods for each test object:

1. It is used for Analyzing the AUT in the initial stage to determine weather the QTP tool is recognizing all of our Application Objects or not
2. We get the logical name of the object.
3. It takes less time to create Tests
4. It helps in identifying the feasibility of automating the application.