QTP/UFT support tip: Test file structure.
There are some cases where a script that was working suddenly stop working, some times it occurs because of a file deleted on the test file structure.
The QuickTest Professional (QTP) test file structure is as follows:
|-- default.cfg - MDRV configuration file; it is needed only for LoadRunner/BAC execution, not for QTP
|-- default.usp - MDRV run-logic; it is needed only for LoadRunner/BAC execution, not for QTP
|-- <TestName>.usr - Main storage for MDRV execution; it is needed only for LoadRunner/BAC execution, not for QTP
|-- Default.xls - Default DataTable
|-- lock.lck - Test lock file (removed when Test is closed)
|-- Parameters.mtr - Parameterization information
|-- Test.tsp - Main document storage (settings) of the Test
|-- Action<i> Folder
|-- ObjectRepository.bdb - The Local Action repository DB file
|-- Resource.mtr - Main document storage of the Action
|-- Script.mts - Action script
|-- SnapShots Folder - Contains Active Screen snapshot files
The following files, if they exist, are obsolete and not created by QuickTest Professional (QTP) 9.0 or above. If you see them, the test was probably originally created by an older version of QTP:
- default.prm - MDRV DataTable. In QTP 8.2 the Data Table was duplicated in this file for MDRV. It is not needed for QTP operation.
- thick_usr.dat and thin_usr.dat - These files are obsolete. They were included from the Astra LoadTest product and were used by MDRV only. They are not needed for QTP.
To ensure that QuickTest Professional (QTP) properly recognize the test folder, the folder structure should remain as listed above. QTP may not open or use the test as expected if files are removed from the structure. If you wish to remove files, verify that QTP will open and execute the test before permanently deleting any files.
This file structure may vary slightly when using Save Test with Resources… functionality available in QTP version 10 when looking into the reusable actions folders.
If you find that this or any post resolves your issue, mark it as an accepted solution.
Note: The Opinions expressed in my post are mine alone, and do not reflect the opinions of my employer.No warranties express or implied for any answerd posted."