Scenario: – We have created new Test with the name “blog” and let us observe the folder structure created by UFT.
Action1:– It contains details about our first Action and is visible in “Editor” (Keyword view of QTP) of UFT.
- Snapshots:-It contains all the snapshots taken during recording of the AUT.It is used when recorded screens are displayed in “Active Screen” in UFT.
- Resource.mtr:-Binary file containing the information for the I/O Parameters of the action.
- ObjectRepository.bdb:– This is local Repository of Action, (Berkeley Database, an oracle Product)
- Script.mts:-Most important of, this file contains the UFT code.
Action0:– it is like storehouse having settings which are applicable to all the actions present in the Test. For instance, “Number of iterations”, “Call to Existing action”.
Lock.lck:-It comes into play, when Test is already opened and it locks the resources of test, such that when we try to access same Test in another instance of UFT , test loads in “Read Only” mode . Thus it solves the concurrency problem, by blocking other user from modifying the already opened test. It has information such as Username, Computer Name and Date details when changes are made to Test.
Default.xls.lck:– It locks the DataTable file, preventing different users to make changes to the same Data file of Test.(It is created only when “Default.xls” file is opened)
TestName.usr (blog.usr):-It is used when working with LoadRunner(HP-Product)
Default.cfg:-This is a configuration file, used with LoadRunner
Default.xls:– Excel file, containing the complete Datatable data.By default it will have two sheets.(Global,Action1).To play with this, open this file, add and save data to “Global” sheet and load the Test again in UFT, added data will reflect in Datatable of UFT “Global” sheet.
Parameters.mtr:-Binary file, which contains information about I/O parameters of Test
Test.tsp:-It is a binary test settings file, contains UFT test settings.
Default.usp:-Again a run logic file for LoadRunner