Manual Testing Working Flow

As per existing project( but beware not tell them you only worked on existing project)  whenever new functionality or new module added to project we are doing the following things.

1. When we got a mock (Requirements documents from clients). 

2. Firstly go thoroughly of docs and writing test cases. 

3. Executing test cases who created behalf of Clients requirements.

4. If found a bug, logging that bugs in bug tracking tools like(Jira, Ticketbuilder,Quality Center).

5. When bug get fixed, again verifying that bug etc.

6. Whenever new build enforces, doing smoke testing for quick test of some major functionality after that doing       regression testing of whole sites.

7. On daily basis whatever the work done by the team, reporting to clients.

8. Assisting to newbie( new member) to get familiar with projects.

9. Providing technical support to team member to setup environment to carryout testing. etc.
10. Carryout chatting, with off-shore QA member to exchange latest information regarding projects. 

Important:  You must remember how to log a bug in bug tracking tools like following

1. A bug have ( Title,Summary or Heading)

2. Priority( Critical, High, Medium, Low)

3. Severity (Show Stopper, High, Medium, Low)

3. Status( Open, Alpha & Beta verified,Inquiry, Build hold, Re-assigned, Assigned,Close, In progress etc)

4. Ticket type( Bug, Re-work, Release, Maintenance, New functionality, Support)

5. Steps to reproduce.

6. Environment(  in my case qa2www.... or on production)

7. Os/ Brow( XP/Vista, win 7, Mac: IE7, 8, FF 3.6, Safari etc)

8. Assignee( either assign to developer or senior QA member for review)

9. Description( here u write, what u actually seeing in bug)

10. Comments( Generally but by qa member and developer)

11. File attachments( screenshot, video file) for bug proof.

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.