Professional Documents
Culture Documents
project.
The activities involves,
Gathering and maintain requirements
Designing the test cases as well as automation test scripts
Test execution (manual test case execution OR automated script execution)
Test coverage
Test execution report
Defect tracking
Quality Center
It is a web based test management tool i.e., we should open it with a browser.
It has 2 applications,
a) QC Admin or QC site administrator
b) QC This is used for end users
Here, the port number is 8080 and siteadmin tool is used only for admin
1|Page
b) Enter the domain name (TESTING your choice) in the textbox
c) Select the domain name (left side) & click on Create Project icon for creating a new project
2|Page
f) Dont change anything in the next window. Click Next
h) Click on Next
---------------------------------------------------------------------------------------------------------------------------------------
3|Page
b) Enter the details of all the users.
c) To set a password
Select User
4|Page
d) To assign a project to a user
Go to Site Projects Select the project
5|Page
Add user to the project and set as project administrator (by checking the checkbox)
From the next section onwards, we will only look into how the end user (testing engineer) uses QC
to manage the entire testing operations
--------------------------------------------------------------------------------------------------------------------------------------
After authenticating the username & password if the username & password is correct the Domain
name & project is generated automatically which has been assigned to the user.
7|Page
QC has 6 main modules namely,
Requirement module
Test Plan module
Test Lab module
Defect module
Dashboard
Business components
Requirement module - this module is mainly used to add & maintain requirements
Test Plan module - this module is used to design test case or test scripts. Also, we can maintain
(modify or change) test case/test scripts
Test Lab module this module is used for test case execution as well as test script execution
Dashboard it shows the current status of the project. It shows what everybody is doing in the
project.
--------------------------------------------------------------------------------------------------------------------------------------
REQUIREMENT MODULE
Normally, the Manager & Business Analyst has access to this module.
But, for studies purpose we shall study this module as well.
1) Click on New Requirement icon (OR) Select New Requirement menu Item from Requirement
menu
(OR)
8|Page
In the above snapshot,
The reviewed field shows whether it should be reviewed by a fellow team colleague or
manager
The type field depicts what type of requirement. Normally, it is software
9|Page
The description field gives the description about the requirement & attaches the necessary
reference documents. There are 3 types of attachments that can be attached such as,
- attach a file
- attach URL
- attach a snapshot
Let us see where the attached files are given in the description,
10 | P a g e
We can see in the attachments section, it has a text file, a URL link, and also a snapshot for the
requirement.
For attaching a snapshot, the attachment camera is taken and click on the application in the desktop
to capture the image for better explanation of the requirement.
After all the details for that particular requirement has been added, click on Submit button. A
requirement unique id is generated for every requirement added.
To see the details of this requirement(or for any other requirement), double click on Amount Transfer
(seen in the above snapshot under name). We get a screen as shown below,
We can see all the details of that particular requirement(including the attachments, the coverage, the
defects found for that particular requirement and also the history of that requirement).
-------------------------------------------------------------------------------------------------------------------------------------
11 | P a g e
Click on New Child Requirement icon by selecting New Child Requirement menu item from
Requirements menu.
For Amount transfer(parent) From Account Number, To Account Number, Amount fields, OK,
Cancel button are all child requirements.
12 | P a g e
To select Child of Child, click on the Child requirement and then click on New Child requirement
After entering all the necessary requirements for Amount Transfer field(refer manual testing notes),
the requirements window looks like this,
13 | P a g e
Now, if we want to arrange the requirements in orderly fashion, we make use of Numeration shown
below,
Thus, we can see that the requirements have been numbered and we can clearly see the parent & child
requirements.
Thus, the test lead can send the requirements to the respective test engineers for writing test cases,
executing test cases and also can assign the requirements to the particular test engineers.
14 | P a g e
---------------------------------------------------------------------------------------------------------------------------------------
Thus, for Amount Transfer, the test plan structure will look something like this,
Subject
- CitiBank
- Tiger
- Manual testing
- Functional testing
- login
- password
- Integration testing
- System testing
- Automation testing
To create New folders -> select Subject folder -> click on New Folder icon as shown below,
15 | P a g e
The structure is shown below,
16 | P a g e
We can see that there are many options for which type of test we want to enter.
Whenever a test is designed in QC, following details are displayed for each test,
1) Details of test case
Header & footer part of a test case will be returned in Details tab
2) Design Steps
The test case body will be added under Design Steps tab
3) If a test case is converted to automated script that information will be displayed under test script
tab.
17 | P a g e
4) All the attachments of a test will be displayed under Attachment tab
5) The requirement for which the test case has been written are displayed under requirement
coverage tab
6) The defect raised because of test case failure can be seen under Linked defects tab
18 | P a g e
---------------------------------------------------------------------------------------------------------------------------------------
19 | P a g e
To remove any step, right click on the step Delete selected item
In the above snapshot, we can see that after step 2, step 4 has been entered instead of step 3.
20 | P a g e
So, we should always highlight the previous step before writing the new step to avoid step
numbering errors.
---------------------------------------------------------------------------------------------------------------------------------------
1) In Test Plan module, select the test case for which the requirements should be mapped.
2) Go to requirements coverage tab -> select the requirements by clicking on Select Requirement
icon.
3) Select the requirement and add to the coverage by clicking on left arrow icon
All the above steps are shown above.
The Direct Cover status of a requirement indicates the coverage of the requirement as shown below,
21 | P a g e
1) if a requirement is not covered i.e no test case has been written, the status will be not covered.
2) if a requirement is covered by test case or test script and the test case is not executed, the status will
be No run
3) if a requirement is covered & the test case / test script is executed the direct cover status will
depend on the status of the test case execution.
We can see another example of not covered status for a new requirement OK button as shown
below,
Thus, we should write a test case for OK button to change the status.
---------------------------------------------------------------------------------------------------------------------------------------
23 | P a g e
- Build number
- Build number
24 | P a g e
To add tests to the group,
1) Create a test set by clicking on New test set icon
2) Add test cases to the Test set by using select test icon
25 | P a g e
Whenever a test case is added to a test set, an instance of the original test case will be copied to the
test set.
A test set can be executed in 2 ways,
Run each test case one by one
Run entire test set at one time
When we click on run for FAN text field(manual), we get the following screen,
26 | P a g e
We get a screen which looks like shown below (we have simulated the run for explanation purposes)
For automated test scripts(TAN text field), when we click on run, we get a screen shown below,
When a test case is failed, a defect can be linked to the test case using linkage option in the test
instance property
27 | P a g e
When we click on linkage & coverage, we get the above field where we can enter the defect.
28 | P a g e
1) open the test case instance which has failed
2) go to linkage & coverage
3) click on link existing defect icon
---------------------------------------------------------------------------------------------------------------------------------------
29 | P a g e
We can see how these are stored as shown below,
They are stored in MS-Excel format as shown below,
31 | P a g e
Easy access
No need to prepare documents for reporting
Test coverage & requirement coverage is very easy
Project status report & analysis is very easy
After script is created, the script can be stored on a Windows File system or QC Server by selecting
Quality Center button in Save Test Window. Browse the location where the script should be stored &
save the script.
32 | P a g e