Quality Center

Introduction :
Tool name : Old version - Test Director by Mercury people.
: New Version - Quality Center by HP people
Type of the tool : Management tool
Company
: Mercury Interactive Incorporation ( now by HP)
Version
: 9.2 ( But we learning 9.0)
Scripting Language : No scripting language is used

Quality center is used for just Management of whole Testing Process

Quality center is NOT used for testing the functionality of the application

Quality Center is a management tool which provides

1. Common Repository
2. Automatic Traceability Matrix
3. Bug Tracking facility
4. Automatic Reports and Graphs generator.
A good Testing Engineer divides Testing process into 6- sections
1. Business Component*
2. Requirements
3. Test plan
4. Test Lab and
5. Defects Management
6. Dash Board
*
: * Not in use
1.Requirements Module: In this section, first we understand all the requirements, once we understood the
what are to be tested, listed out all the Main Requirements as well as sub-requirements (child
requirements).
=> For every Requirement we need to plan a Test.
* Test means Test case (in manual) or
* Test means Test Script (in Automation)
This module used for building the requirement string. To do the same
this module has provided Two options
a). New Requirement
b). New Child Requirement
These two requirements will do the following
i). One can attach any kind of attachments to the requirement
ii). It will automatically shows the author name
iii). It will generate IDs automatically for each and every requirements
iv). One can give direct cover status of the requirements like
Whether the test is covered or Not
Whether its executed or Not
If executed, whether its passed or Failed

Requirement Module
MR1
CR1
CR2

MR2
CR3
CR4

MR : Main Requirement
CR : Child Requirement

2.Test Plan Module : In this section,

1. We need to create test plan for corresponding requirements which were prepared in
Requirement module.
2. Using the Traceability matrix, you should cross check whether you have created test
plans for all the requirements.
Test Plan Module
This module is used for creating the tests (automatically or manually for
all the requirements ) to do the same one has to create a folder, under that
he needs create the desired empty test. Based on the test one has to launch
the corresponding functional tool (QTP), generate the desired test scripts
and Click on the save Button in the functional tool.
The script will be saved in the empty script file which is already
created in the Quality center. In the same way one has to create all the
tests. Once all the test are created this module also provides the facility to
establish the link between the test and corresponding requirements with
help of requirements coverage tab in order to establish automatic
traceability and its feasibility.
Once all the test are created then one will go to next module
by name Test Lab.

MT1
CT1
CT2

MT2
CT3
CT4

MT : Main Test
CT : Child Test

3.Test Lab Module : In this section, First of all we need to identify all the end-to-end scenarios , then for each
end-to-end scenarios we will create a Test Set.
This module is used for the following
1. Building the Test set
2. Execute the Test set
3. Analyze the results.
1.
To do the same one has to Build/ create the folders and create corresponding test sets with help of all the
available test sets based on the different end-to-end scenarios .
2.
Once the tests are Build one can Execute them by either RUN or RUN ALL options provided in this
module.
RUN : is used for Running a single selected test in the test set
RUN ALL : is used for running all the tests in the test set
3.
Once the execution is completed one can analyze the Results in the Functional tool (QTP) it self and if
at all one can identify the Defects and need to post them , he can do it from the Functional tool itself, other wise,
go to next module by name Defects Module.

4. Defects Module : This module acts like Bug Tracking tool and provides all the facilities to manage the
defects like Adding the defects, changing the status of defects etc., with complete bug tracking facility is
provided.

Once the Defects (if any) are been sent to Developers, they will re-build the application by removing such
defects and send it again for Testing.
This is called 2nd Build, doing testing on 2nd build on wards is called Re-Testing or Regression testing.
Here we do testing from 3rd module (Test Lab Module) to 4th module (Defects Module).
Till all the defects have been fixed.
So that we will have a proof for every related tasks ( above 4-modules).
Then we can say that we have done a GOOD Testing.

Architecture for Quality Center :

Requirements Module
Plan a Test by
Creating MR
Creating CR

Test Plan Module

Creating
corresponding test
plans for
requirements.
Creating MT
Creating CT

Test Lab Module

Defects Module

Creating Test Set for

each end-to-end
scenarios.

Bug Tracking

Building Test set

Executing Test set

Changing status..
etc.

Adding defects

Normal testing flow

Re-Testing / Regression testing

A Test Engineer expects from a company to work for testing.

1. Common Repository :- Its a centralized system / server wherein authorized persons can store the
data related to testing.
2. Automatic Traceability Matrix :- if possible to company (optional )
3. Default /Bug tracking tool :- To manage the defects easily. Some companies are maintaining their
own tool in this case.
4. Automatic Reports and Graphs generator : if possible to company (optional )
Due to cos,t most of companies are not using Quality center tool, But, maintaining their Own systems for all
above 4 operations.

Extra Components / modules in Quality Center :

5. Business Component* : It is a special feature or module provided by Quality Center in order to perform
Business Process Testing. In this type of testing usually the subject experts i.e business analysts
will develop the business components based on the business flow of the application and then
Automated test engineers will build the script in them. So that one can perform testing in an even
more effective manner.
6. Dash Board* : Its a special component provided by quality center which is used for generating the reports
across multiple projects at a time. Usually this facility will be used by Managers.

Site Administrator
Site Administrator is a very important component provided by Quality Center which is
used for following
1. Creating new users
2. Deleting old users
3. Modifying the information of the users
4. Creating the Domain
5. Creating the projects i.e allocating the space for new projects in the server/ common resources area
6. Assigning the users for the project and all other administrative activities.

* We write Functions in Quality center in such way that to open Test script in QTP and when we save it that
will be saved in Quality center.
* Scripts cant be written in quality center.
* Scripts cant be executed in quality center.
** Two ways we can test the application
1. Thru QTP : By giving the path in QTP for quality center.
2. Thru Quality Center : by opening QTP from quality center.

Write some script in test pane ( say: msgbox Hai)

Save it to hard disk or
If thru quality center a Connection must be established.
Open Tool -> File -> Quality Center Connection
It will ask for Server name or url , give the name as required
Give the username and password
Select the domain name and project , click on Login button
Now connection is established.
Now click on Save the file option , so that it will be saved in quality center
If you want you can Retrieve the saved file by selecting file -> Open option
If you want to Logout, select File -> Quality Center -> Logout -> Change user -> Disconnect.

-: The End :Pls. leave your feed back (both +ve and ve ) at kanakadria@yahoo.co.in