Skip to main content

QTP - File Formats

Lot of QTP users are very interested to know all file formats related to QTP. Here are list as of my knowledge. Kindly do correct me if I am wrong.

Inside each Action:
-->  .BDB - Berkeley  Data Base - This is the Local Object Repository
-->  .MTR - Mercury Test Resource - This file contains Resources i.e. External Libraries, ORs and other files associated to each action.
-->  .MTS - Mercury Test Script - This is the script belongs to particular action.
-->  Folder Snapshots - Used to store the Active Screen images for the action.

Inside each Test:
-->  Actions folder will be there.
-->  default.CFG - Contains full details about run configurations
-->  default.USP - Contains user info with run logics. (related to LoadRunner execution)
-->  test.TSP - Used to store test settings info.
-->  Parameters.MTR - Contains Input, Output parameters info belongs to the test.
-->  TestName.USR - This file contains info about add-ins, files associated, environment info and other files info belongs to the test. (related to LoadRunner execution)
-->  test.lck - Lock file for the test if anyone is using the test.
-->  default.xls - Test Data file i.e. default DataTable associated for the action.

--> .TSR - Test Shared Repository
--> .QFL - QTP Function Library. Just custom QTP format instead to use common .VBS
--> .QRS - QTP Recovery Scenario


  1. Thanks for sharing great information in your blog. Got to learn new things from your Blog . It was very nice blog to learn about Selenium


Post a Comment

Popular posts from this blog

QTP - Object Identification - Prerequesties

While starting a new project or proof of concept or after new QTP installation, we would face the issue in identifying objects as QTP built objects like WinList, WebEdit, etc.; instead everything will be identified as WinObject.

Here are some steps to ensure you did the environment setup RIGHT before start automating.
Did you enabled required Add-ins only while launchingDid you selected "Record >> Record and Run Settings" - This should be based on what type of application you are working with
Windows app - Windows >> Record and run test on any windows applications. Web app - Web >> Record and run test on any open browser.
Did you tried to launch UFT/QTP and then AUT.If its web, ensure browser zoom level set to 100%Try disabling the protected mode in IE for web.Launch UFT and AUT using RUN AS ADMINISTRATORAlso see the Object Identification Methods if you are interested.

Change IE Browser ZOOM settings

Lot of UI automation testers could have faced this problem as we could change the zoom settings while operating manually for our convenience and forgot to reset to 100%.
But our QTP and some other related tools would operate the browser perfectly if browser zoom is 100%. So wee need to change the zoom before start to run the scripts. Its better to have a code snippet in our framework to change this zoom setting right?
Here we go...

1. We can simply change the Registry values before Invoking IE
Function ChangeRegistry Dim objShell Set objShell = CreateObject("WScript.Shell")  objShell.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Zoom\ZoomFactor", "100000", "REG_DWORD" Set objShell = Nothing EndFunction This option is very useful. But in real time, lot of customers could have restricted write access to windows registry. So we can try other options.

2. Use IE COM object and Change Settings
Function ChangeIEZoom Dim intZoomLevel, objIE  intZoo…

Run JavaScript from QTP

Yeah, You can run your pure JavaScript from QTP using RunScript method. Lot of times, we are in need of firing events or simulating actions on web page which is not supported by QTP. At that time, you can use your direct DOM methods and directly execute your script on the web page from QTP like,
Dim MyPage, SearchBox Set MyPage = Browser("title:=Google").Page("title:=Google") Set SearchBox = MyPage.RunScript("document.getElementsByName('q')(0);") SearchBox.Value="testing"
'if objects available in frames, Set SearchBox = MyPage.RunScript("document.frames(4).document.getElementsByName('q')(0);")
Set objFrame = Browser("title:=Google").Page("title:=Google").Frame("title:=something")
objFrame.RunScript("document.getElementsByName('q')(0);") Also, you can execute by obtaining actual browser window object if you have IE app like, Dim IEApp Set IEApp = CreateObject("Internet…