UFT(QTP) difference between Action0 and Action 1|QTP script contains two sub folders “Action 0” and “Action1” by default , Why ?


QTP script contains two sub folders “Action 0” and “Action1” by default , Why ? |UFT(QTP) difference between Action0 and  Action 1

By default each QTP script contains two sub folders “Action 0” and “Action1”. If we increase the number of actions then the number of the subfolders will increase accordingly. However please note that changing the name of action will not result into change of the sub folder names.

Following is the directory structure:







1111. Action 0: Only Script.mts file is useful in this folder. This file contains the call to the actions and the no of iterations on which the action has to iterate. We can also add code here.


2. Action 1:
a. Snapshots: This folder contains the snapshot of the application  taken during recording. . It contains the ‘HTML, XML & PNG files
b. Objectrepository.bdb ( BDB = Berkeley Data base, an oracle product): This is the local object repository of the action
c. Resource.mtr: This is a binary file and contains the information about the action IO parameters and similar action info.
d. Script.mts  (Script files): This file contains the QTP code.

3. Default.xls (Default Excel file): This is the default xls data file of the test script

4. Default.cfg (Configuration file): Configuration file of the script mainly for the loadrunner

5. Lock.lck (locks the file opened by QTP Script): It locks the open files of the test. If a script is open at one machine. Then it locks that script so that it will open only in read mode by other machines or by qtp script editor.
Interesting Note: If you make this file read then QTP script will always open in read only  mode. To enable the editing mode back you need to remove the read only mode from the lock.lck file.

6. Parameters.mtr:  It contains the test script IO parameters info.

7. Test.tsp  (test settings): A binary file not sure about but most probably contains the QTP test settings.

8. ScriptName.usr: Loadrunner file

9. Default.usp:  Loadrunner file

Comments

Post a Comment

Popular posts from this blog

UFT File Types and File Extensions

QTP Script File            :    .mts  ( mercury test script) QTP Local Repository  :    .bdb (berkely database) Shared Repository        :    .tsr ( test shared repository) Load test configuration file : Default.cfg Load test configuration file  : Default.usp Test Settings File -------- Test.Tsp Test Parameters file ---- Parameters.mtr Input / Output Data Datatable  ( Excel file) ---Default.xls Resource.mtr- ------- contain the resources associated information like function library, recovery, shared repository(mercury test repository) Recovery Scenario   -------- .qrs Function library- ----------.vbs / .qfl / .txt Batch Test-- -------------  .mtb Action Template ---------  .mst ( mercury shared template) Virutal Object- ---------  .vot  ( virtual object template) lock.lck-- ----------- Created when the QTP test is open Environmental Variable Files ------- .txt, .ini, .xml
Read more

QTP/UFT Version History

What is QTP (UFT)? QuickTest Professional, popularly known by its acronym QTP is an automation testing tool originally from Mercury Interactive which was acquired by Hewlett Packard (HP) in 2006. QTP is primarily used for functional and regression automated testing. Using QTP, you can automate user actions on a web or client based computer application and test the same actions for different users, different data set, on various Windows operating systems and/or different browsers. Automation using QTP if planned and executed in a proper manner can save considerable time and money. With the release of version 11.50, QTP and Service Test became part of UFT 11.50 software. QTP is one of the most widely used automation testing tools in the market today with over 60% market share. Due to this reason, skilled QTP professionals are always in demand. Version history of QTP:- Astra Quicktest (First version) The first version of QTP was named Astra QuickTest and it was released by Mer
Read more

Synchronization in UFT

Image
When we automate the script most of the time we faced several issues with performance of application. sometimes application becomes slow in response sometimes fast. then how we show make sure that our script should run in irrespective of the application performance and response? all automation tools provide specific functions which handles these performance issue. UFT also has Synchronization mechanism to make sure that script will not fail. Lets discuss more about the Synchronization. There are 5 different ways to handle the synchronization. WaitProperty Exist Wait Sync(only for web based apps) Default Synchronization WaitProperty: WaitProperty is a method  which can be apply on any object in UFT. It takes the property name, Value and Timeout value as input to perform the sync. It is a dynamic wait, it means once the object is get visible/enable or state becomes true corresponding action gets performed. so it is highly recommended options. Example : lets put wa
Read more