Monday 30 July 2012

Types of Recording in QTP

a) Test Recording Process

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.

b) Running /Execution Process
During Running QTP reads statements one by one and gets Object Information from the Object Repository, based on that Information performs operations on AUT.

c) Recording Modes
QTP has 3 Recording Modes to generate Tests / Test Scripts

i)  Normal Recording 

It records User Mouse and Keyboard operations on AUT with respect to objects, but unable to record continuous mouse operations like Digital Signatures, graphs, paints etc.

During recording QTP generates VbScript statements in Test Pane, Simultaneously it stores objects information into object repository. 

Navigation: Automation>Record

                          Or

           Select Record option on automation toolbar

                          Or

             Use short cut key (F3) 

Steps for preparing a Test (through Recording): 

1.Put AUT in base state

2.Select Record Option

3.It shows Record and Run Settings, Select type of Environment (Windows or Web)

4.Select Record Option  

(It shows two Options :

1.Record and Run Test on any open window based applications

2.Record and Run only on) 

If we select first option it records on any opened application on Desktop.

If we select Second option, it asks for the path of the AUT, After Providing the path it records only on that particular application.) 

5.Click OK

6.Perform actions on AUT

7.Stop recording.

8.Save the Test  

ii) Analog Recording: 

It records the exact mouse and keyboard operations. We can use this mode for recording continuous mouse operations. It is not useful for recording normal operations why because it does not generate steps for each operation, generates total user actions in a Track File. The Track file is not editable. 

Navigation:  

1.Keep tool under recording mode

2.Automation >Analog Recording

OR

Use Short cut Key (Shift + ALT+F3) 

Steps for preparing a Test (through Analog Recording): 

1.Launch AUT (or we can launch AUT through QTP)

2.Select Record option

3.Automation>Analog Recording

4.Analog Recording Settings Dialog box opens 

(In this Dialog box two options available. 

1.Record relative to the screen

2.Record relative to the following window) 

(If we select first option QTP records User operations with respect to Desktop co-ordinates.

If we select Second option, we have to show the window (AUT), after showing the Window it records with respect to that window co-ordinates.) 

5.Select any one option in the dialog box and click Start Analog record.

6.It records User actions

7.Stop Recording

iii) Low Level Recording 

It records some operations on Non-supported environments apart from Normal operations.  

This mode records at the object level and records all run time objects as window or winobject Test objects. 

Use Low Level Recording for recording in an environment not recognized by QTP. 

Navigation:

1.Keep tool under recording mode

2.Automation >Low Level Recording 

Steps for preparing a Test (through Low Level Recording): 

1)Launch AUT (or we can launch AUT through QTP)

2)Select Record option

3)Automation> Low Level Recording

4)Perform options on AUT

5)Stop Recording

6)Save the Test 

d) Disadvantages of Recording
• It occupies a lot of memory space(due to duplicate objects), So QTP    performance will be reduced 

• No Centralized Maintenance mechanism , So Modifications are very difficult 

• User may not have command on the Recorded script, So locating errors is difficult 

•  Recorded scripts are QTP internal files, they may corrupt.


e) Advantages of Recording/ Where Applicable
• It is used for Analyzing the AUT in the initial stage to find out weather the QTP tool is Recognizing all of our Application Objects or not

• It is easy to create Tests / Test Scripts 

•It is used for frequently changing UI (User Interface) 

• It takes less time to create Tests


No comments:

Post a Comment