Anatomy of Quick Test Professional9.1

As Part of the QTP9.1 QTP screen has been divided into 7 parts.

• TEST PANE
• ACTIVE SCREEN
• DATA TABLE
• DEBUG VIEWER PANE
• TOOL OPTIONS
• INFORMATION PANE
• MISSING RESOURCES PANE

Test Pane: Test Pane is an area provided by QTP to view the test script and it also allows the user to do any kind of modifications to the script. It’s represents the script in 2 views.

• keyword view
• expert view

Expert View: Expert View represents the script in VB Script format.

Keyword View: It represents the script using a Graphical User Interface (GUI).

Active Screen: Active Screen is a feature provided by QTP which holds the snapshots of each and every script statement and used for the following
· It is used for understanding script easily.
· It is used for enhancing the script easily.

Data Table: Data Table is also called “Formula One Sheet”. Developed by the third party and integrated with the QTP and used for the following

1. It is used for holding the Test Data.

2. It has a capability of importing the Test Data from different data sources like Excel Sheet, Data bases, Flat files.

3. It isolates the Test Script from the data source.

4. It provides an API to interact with the Data directory.

QTP maintain 2 copies of Data Tables.
· Design Time Data Table.
· Run Time Data Table.

Debug Viewer Pane:

Debugging: Debugging is a process of executing the script or a program in a user designed fashion. with some temporary breaks in order to identify the errors.

Debug Viewer Pane used for viewing, modifying, setting the current values of the variables during the execution breaks using 3 tabs by name watch expressions, variables and command.

Tool Options: All the remaining things in QTP window are under Tool Options.

Information Pane: This Pane is shows the any syntax error in the Test Script.

Missing Resources Pane: This Pane shows if any resources like shared repositories, library files, recovery scenorio files are missied then this pane indicates that there is some resources are missed.

What is Quality Assurance

Quality Assurance is a process. in which each and every role is monitered and guided right from the starting of the process to till the end of the process. Usually they do the verification during the process.

Software Development Process Models

There are Many Software Development LifeCycle Process Models. Following are the Famous Models.

• Water Fall/Sequential Model
  
• Prototype Model
  
• Evolutionary Model
  
• Spiral Model
  
• Fish Model
  
• V-Model
  

WaterFall/Sequential Model:This model is used when the Client is very much clear with Requirements.This Waterfall/Sequential Models is sequential.After completion of one phase then only other phase is starts.The main drawback of this model is we can't go back to previous phase.


Prototype Model:This model is used when the Client is not clear with Requirements. In this Model companies will develop the prototypes and demonstrates to the clients and gathers clear requirements from the Clients.After Gathering the Clear Requirements they will continue with the Waterfall/Sequential Model.


Evolutionary Model:This model is used when the Client is keeps evolutes the requirements. Every time clients evloutes the requirements and gives the feedback with new requirements. In this model every time the Application is validated.

Water Fall model

Water Fall model is one of the famous Software Development Process Model. This Model is used when the Customer is very much clear with the requirements.This Model is also called as a Sequential Model.

Levels of Testing:

There are five levels of Testing.
1. Unit Level Testing
2. Module Level Testing
3. Integration Testing
4. System Testing
5. User Acceptance Testing (UAT)

Unit Level Testing: If one performs Testing on the smallest part of an Application (units) then that level of testing is known as User Acceptance Testing, it is White box Testing and usually done by the Developers (or) White box Testers.

Module Level Testing: If one performs Testing on a Module then it is known as Module Level Testing, it is a Black box Testing and usually done by the Test Engineers.

Integration Testing: Once the modules are ready the developers will combine these modules with some programs (links) and test weather the modules are integrated properly or not, it falls under White box Testing. Usually it is done by Developers or White box Testers.

Integrating the Modules can be done in Four Approaches
1. Top – Down Approach.
2. Bottom – Up Approach.
3. Sand – Witch Approach / Hybrid Approach.
4. Big bang Approach.

System Level Testing: If one performs testing an Application after installing (deploying) it in to an environment is known as “System Level Testing”, it is Black box Testing usually done by the Test – Engineers.(System Integration Testing).

User Acceptance Testing: If the same System testing is done in the presence of user then it is known as “User Acceptance Testing”. It is a Black box Testing.