Академический Документы
Профессиональный Документы
Культура Документы
Prepared By Sriraman K
Objectives
2
Test Management Tool
3
Test Management Overview
Definition
• “Manage and measure the application delivery process
from a quality perspective”
Process
• Validate application functions against the functional
specification, i.e., functions yield the expected results?
• Report and track defects
• Measure test coverage and track application quality
4
What is Test Management Tool
5
Why Test Management Tool
6
Benefits of Test Management Tool
• More consistent
• Reliable in compilation of reports
• All the reports are instantaneous and hence the
status of delivery is clearly visible to
management.
• Security
• Traceability Matrix
• Managing Change Request
7
Caution
8
What are the different tools available
in the market (for functional
testing)
• Rational Clear Quest
• Rational Test Manager
• Silk Central
• HP Quality Center
• Open Source Tools – Bugzila, Jira etc.
9
Introduction to QC
10
Add Ins of QC
• For integrating with automation tool like QTP,
Winrunner, QC requires Add in
– By Default QC supports
• Winrunner
• LR
– Other Addin
• QTP
11
Course Objective
• Site Administrator
– Managing Domain • Quality Center
– Managing Projects – Release & cycle
– Managing Users
– Making user as – Requirements
Administrator to the project • Managing Requirement
– Site Connections • Customizing Requirements
– License • Reports
– Site Analysis – Test Plan
• Quality Center – Test Lab
– Customization
• Users – Defects
• Groups
• Module Access • Export From XLS
• Project Entities
• Project Lists • Export From Word
• Requirement Type
• Risk Based Quality Management
• Auto Mail
• Traceability
• Alert
12
Site Administrator
• Manage Domain –
– Domain is a folder which can handle any no. of
projects.
• Create Domain
• Rename Domain
• Manage Projects
– Projects are the specific project by itself, whose
Requirement, test case and defects needs to be
maintained.
– Each project is an database by itself
– Cannot link one project to another project
13
Projects – Contd.
• Manage Project
– Creation of Project
– Renaming a Project
– Pinging a Project
– Coping a Project
– Managing users to the project
– Making an user as Administrative user for a project
• Manage Users
– Creation of Users
– Association of users to the projects
14
Quality Center
• Customization
– Project Users
• Assigning users to the project
• Creation of new user to the project
• Mapping groups to the users
– Project Groups (what is groups and its importance)
• Creation of Groups
• Assigning users to the groups
• Customizing control using groups
– Field level control
– Setting the permission to change the data by created user and other
user
15
Customization contd.
• Module Access
– Controlling license using Module access
– Need of Module Access
• Project Entities – Works with Database Tables
– System Defined Fields
• Change Logical name for existing fields
• To configure history, Mandatory and searchable criteria to a
field
– User defined fields
• As String
• As Date
• As Number
• As Blob
• As List and User List
16
Customization Contd.
• Project Entities
– How to make a field as mandatory (Required)
– How to make a history to a field
– How to give formatting to a field
– How to include the field for search
– Creation of User defined field
• Mapping the field as String, List, UserList, Blob, Number
• Formatting the field (Masking)
17
Customization – Project Lists
• Project List
– Creation of New List and configuring the list using
project entities
– Managing the existing list with new values
– Importance of checking the check box as Verify value
of the project list in project Entities
– Controlling the work flow for a list box contents using
Groups
– Effect of those in Requirements, Test Plan and Defects
18
Requirements
• Requirements
– Creating a Requirement
– Creating a sub requirement
– Testing the changed workflow in the project groups in
requirements
– Testing the Mandatory, history setting at project
groups
– Customizing the columns
– Different views of Requirements
• Coverage view
• Grid view etc.
19
Test Plan
• Test Plan
– Creation of Test Scenarios (Folders), Sub Folders
– Creation of Test Cases under Folders
– Checking the effect of permission by changing the
setting in groups for various users.
– Customizing user defined field and its effect under
test plan
– Test Plan Details
– Different View for Test Plan
– Mapping Test cases to the requirement
– Reports – Summary, Progress, Trend
20
Test Lab
• Test Lab
– Creation of Rounds (Folder)
– Creation of Test Set
– Mapping test case to the test set
– Execution of Round
– Finding the actual result in the requirement after
mapping
– Creation of defect while executing through execution
screen
– Different execution reports
21
Defects
• Defects
– Creation of Defects
– Managing the defect cycle by configuring through groups
– Effectiveness of security features of the defect status change
– Customizing defect for various groups
• Customizing the add defect screen
• Customizing the modify defect screen
– Various defect reports
• Defect aging
– Linking defects – Requirements, Test case, Through test lab
22
Export From XLS file
23
Export From XLS Contd.
24
Export From XLS Contd.
25
Export From XLS Contd.
26
Export From XLS Contd.
27
Export From XLS Contd.
– Click on finish
– Go to QC and we can
see the Requirements
got added.
– Same way we can do
for defects or Test Case
28
Export From Word
29
Export From Word Contd.
• Requirement Adding
– Click Open req. Icon.
– Enter the Requirement Name and
Press Enter
– Click Description
– Enter Description and press Enter
– Click Review
– Enter Review value (as in the list
box) (same way for author, priority)
– Enter Author (as in the list box)
– Enter priority (as in the list box)
– Click Close Requirement
30
Export From Word Contd.
31
Export From Word Contd.
32
Export From Word Contd.
• Once done,
Click on Export
To QC icon
• Select the Server
• Enter UserName
and Pass word
33
Export From Word Contd.
• Select the domain and Project for which import has to happen
• Select Next and finish
34
Export From Word Contd.
• Go to QC
• Login and you can see
the requirement added
35
Export From Word Contd.
• In the test
plan module,
you can see
that test
folder and
test cases
with test
steps got
added.
36
Application Programming Interface
• What is API
– It is an Application Programming Interface
• Need of API
– Company cannot customize for every customer certain
workflows or controls due to specific requirement of
that client.
– Customizing for individual customers leads to poor
product maintenance in long run as product.
– Product release and version control gets affected by
customizing to individual customers at release level
37
API Contd.
39
Comments & Queries-
sriramank@softsmith.com
Or
webinar@softsmith.com
40
Feedback-
Contact Details
Sriraman K
Email : sriramank@softsmith.com
41