QTP Directory Structure3?

TestName> Folder
     |
     |-- 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
     |-- .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 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.x. If you see them, the test was probably originally created by an older version of QTP:

QTP Directory Structure2?

1.

2.   a. Action folders : ....
      b. Files inside the :

• .cfg file -This holds the run time information like addins loaded user information etc.
• .prm file -Hlds the information about the number of iterations and the parameters that are used within the script / action.
• .usr file -This will be generated to hold the name of the script the object repository info etc.
• .lck file -This is a lock file.
• .mtr file -mercury test repository basically used for batch testing
• .xls sheet -The default sheet that holds the parameters used within the script.
• .prm.bak file -backup file.
• .usp file -Stores some RUnLogic information for the script.
• thin_usr.dat file -similar to the thick usr file. The diff is not clear exactly.
• thick_usr.dat file -Stores high level info about all the above and below files indicating what set of files was created etc.
• .tsp file -Main document storage (settings) of the Test

3. folder:
This is a default folder that is created to hold the following:

• folder:This will hold all the active screen files which are zipped pertaining to that action.
• Resource.mtr file -This file holds info regarding the object rep used the shared libraries used and possibly maitains a track of how the script is being accessed through the code. Ie. the call chain.
• Script.mts -This is the script file actually.
• .tsr -The object rep file if used in per action mode.
• The result file.
• The action excel sheets.

QTP Directory Structure1?

When saving a test, you assign it a name. A test name directory is automatically created and all the files related to the test are saved in the test name directory. By default, QuickTest creates certain files and directories in each test directory.

• ACTION0: This directory contains files that control all actions, except ACTION0, in the test directory.
• ACTION1: This directory contains a log of user actions on objects as these were captured during recording.
• SCRIPT.MTRS: This file captures the user actions on objects. This file resides in the ACTION1 directory.
•  DEFAULT.XLS: This file contains the data that you specify in DATA TABLE to parameterize your test.

QuickTest Professional enables you to compress the test folder to conserve hard disk space on your computer and to ensure easy transfer of tests within a network or over the Internet. To compress the test name folder:

1. From the QuickTest Professional menu bar, select FILE → EXPORT TEST TO ZIP FILE. The EXPORT TO ZIP FILE dialog box appears.
2. In the EXPORT TO ZIP FILE dialog box, specify the path where you want to save the zip file, and click OK. 

STLC?

It is a process of conducting software testing, means after 
programmer conducted integration testing by using white 
box testing, the integrated software build is coming to 
overall developed software testing. 

Test Requirements

• Requirement Specification documents
• Functional Specification documents
• Design Specification documents (use cases, etc)
• Use case Documents
• Test Trace-ability Matrix for identifying Test Coverage

Test Planning

• Test Scope, Test Environment
• Different Test phase and Test Methodologies
• Manual and Automation Testing
• Defect Mgmt, Configuration Mgmt, Risk Mgmt. Etc
• Evaluation & identification ? Test, Defect tracking tools

Test Environment Setup

• Test Bed installation and configuration
• Network connectivity?s
• All the Software/ tools Installation and configuration
• Coordination with Vendors and others

Test Design

• Test Traceability Matrix and Test coverage
• Test Scenarios Identification & Test Case preparation
• Test data and Test scripts preparation
• Test case reviews and Approval
• Base lining under Configuration Management

Test Automation

• Automation requirement identification
• Tool Evaluation and Identification.
• Designing or identifying Framework and scripting
• Script Integration, Review and Approval
• Base lining under Configuration Management

Test Execution and Defect Tracking

• Executing Test cases
• Testing Test Scripts
• Capture, review and analyze Test Results
• Raised the defects and tracking for its closure

Test Reports and Acceptance

• Test summary reports
• Test Metrics and process Improvements made
• Build release
• Receiving acceptance