Ø
Developed by Mercury Interactive and taken over
by HP
Ø
Quality Centre was previously called as Test
Director
Ø
Quality Centre is a Test Management Tool to
store all the testing documents such as Test Strategies, Test Plans, Test Scenarios,
Test Cases Documents, Test Data, Review Reports, Automation Scripts, Test Logs,
Defect Reports in a secured database
Ø
Test Engineers are using QC instead of MS Office
for documents preparation in IEEE 829 format/templates, these documents are saved
in QC database, and this database can be saved and recovered easily
QC TOOL ARCHITECTURE: HP QC tool works like a website within the
company network. To open QC tool pages
or screens, people must use a browser called QC EXPLORER. Hardware team can install QC software in
Server Computer and QC Explorer Browser in the respected client computers
within the company network
There are only TWO SCREENS in QC No.1 SA
BIN and No.2 QC BIN
QC
Software will be installed in Server Computer on Windows 2003 Server or Windows
2008 Server as O/S
QC Explorer Browser will be
installed in respected client computers on Windows XP, Windows Vista, or
Windows 7. People must use QC Explorer
browser to access QC software screens/pages from the server. QC Software does have only two pages such as
SA BIN & QC BIN (System Admin Binary & Quality Centre Binary)
SA BIN Page can only be accessed
and used by Networking Admin to do his responsibilities. QC BIN Page can be accessed and used by rest
of the people on the current project with restricted admin rights
NETWORK ADMIN RESPONSIBILITIES
A) Creating
user IDs for new employees. Network
administrator must follow the below navigation to create user ID and password
for the new employees
QC EXPLORER: NEW EMPLOYEE REGISTRATION
Ø Open
QC Explorer
Ø Select
SA BIN
Ø Click
“GO”
Ø Login
by Network Admin
Ø Click
site users
Ø Click
new user icon
Ø Allow
new employee to create a unique login ID
Ø Allow
new employee to create a password
Ø Click
“OK”
Ø “LOGOUT”
NOTE: The above registration is mandatory for every
new employee.
B) CREATE
DATABASE IN SERVER
When a new
project/product is finalized, network admin can create an empty database in
server computer by using oracle or SQL server.
Testers can use that database to store all testing documents
QC EXPLORER
NAGIVATION TO CREATE DATABASE
Ø Open
QC Explorer
Ø Select
SA BIN
Ø Click
“GO”
Ø Login
by Network Admin
Ø Select
Site Projects
Ø Select
domain or create a new domain
Ø Create
a new project
Ø Select
empty project option
Ø Click
“NEXT”
Ø Browse
current project name from the server to create an empty database list
Ø Click
“NEXT”
Ø Select
database technology either oracle or SQL
Server (by default)
Ø Enter
server computer name
Ø Click
“NEXT”
Ø Select
Test Lead user name as project admin
Ø Click
“NEXT”
Ø Click
“CREATE”
Ø Click
“OK”
Ø Logout
NOTE: In general, Test Lead category people are
getting selected as Project Admin, they also called as “TD ADMIN” or “QC ADMIN”
TEST LEAD RESPONSIBILITIES:
A) LOGIN: In general, TD Admin/Test Lead
responsibilities begins with LOGIN into server database
QC EXPLORER:
Ø Open
QC Explorer
Ø Select
QC BIN
Ø Click
“GO”
Ø Login
by Test Lead to access respected Project/Product
Ø Click
“CLOSE” welcome screen after successful login
B) ADD EMPLOYEES TO PROJECT WITH
DIFFERENT ROLES
After successful login, responsible
Test Lead can follow the below navigation to add employees to new project with
different roles such as PM, Developer, QA Tester, and Viewer. Here Test Lead role is “TD Admin”
TOOLS MENU (AFTER LOGIN BY TD
ADMIN)
Ø Customize
Ø Project
Users
Ø Select
“Add User” from list option
Ø Select
user from list and provide role
Ø Follow
above navigation to add more employees to a new project/product for different
roles
Ø Click
“SAVE”
Ø Click
“OK”
Ø Click
“RETURN”
C) RESPONSIBILITIES FOR DIFFERENT
ROLES: After completion of employees
roles selection, respected test lead can provide responsibilities to their
roles
TOOLS MENU (AFTER LOGIN BY TD
ADMIN)
Ø Customize
Ø Module
Access
Ø Select
“Components” for different roles
Ø Click
“SAVE”
Ø Click
“OK”
Ø Click
“RETURN”
ROLES AND RESPONSIBILITIES MATRIX
ROLES
|
REQUIREMENTS
|
TEST PLAN
|
TEST LAB
|
BUSINESS COMPONENTS
|
DEFECTS
|
MANAGEMENT
|
PM
|
Y
|
Y | Y | Y | Y | Y |
Test Lead
|
Y | Y | Y | Y | Y | Y |
Developer
|
X
|
X
|
X
|
X
|
Y
|
X
|
QA Tester
|
Y | Y | Y | Y |
Y
|
X
|
Viewer
|
Y
|
X
|
X
|
X
|
X
|
X
|
D) ALLOCATION OF MODULES or
REQUIREMENTS TO TESTERS (WBS)
Ø Requirement
Components
Ø Requirement
folder
Ø Requirement
menu
Ø New
requirement
Ø Select
requirement test as testing
Ø Enter
module name as “required” (exp: login)
Ø Click
“OK”
Ø Select
responsible tester as “Author”
Ø Click
“Submit”
Ø Click
“Close”
Ø Follow
the above navigation to allocate all modules to testers
Ø Logout
Exp:
Login
-------------ID1--------------Tester1
CD -------------ID2--------------Tester2
MT -------------ID3--------------Tester2
MS -------------ID4--------------Tester1
LOGOUT--------ID5---------------Tester1
E)
SELECTING TESTING TOPICS:
After completion of modules
allocation to responsible testers, corresponding test lead can assign
responsible topics for allocated modules, such as functional testing, usability
testing, compatibility testing, hardware configuration testing, …etc.,
Ø Test
plan component
Ø Test
menu
Ø New
folder
Ø Enter
responsible testing topic name as folder name
Ø Follow
above navigation to create all responsible testing topics as folders
Exp: Topic
Functional Testing
Non-Functional Testing
Usability
Testing
Compatibility
Testing
Performance
Testing
“ “ Load
Testing
“ “ Stress
Testing
“ “ Spike
Testing
Soak
Testing
F)
DEFINING TEST EXECUTION LEVELS
Ø Management
Component
Ø Release
Menu
Ø New
Release Folder
Ø Enter
Current Project Name as Folder Name
Ø Click
“OK”
Ø Release
Menu
Ø New
Release Folder
Ø Enter
Current Version Number of the Project Build as Release Name
Ø Click
“OK”
Ø Release
Menu
Ø New
Cycle
Ø Enter
Text Execution Level as Cycle Name
Ø Click
“OK”
Ø Follow
above navigation to create cycles for all software build versions
Exp:
PROJECT/PRODUCT
Version 1.0
Smoke
Test
Real
Test
Version 2.0
Smoke
Test
Retest
Sanity
Test
Regression
Test
“ Further Test
“
“
Version N.O
Smoke
Test
Retest
Sanity
Test
Regression
Test
Final
Regression Test
TEST ENGINEER RESPONSIBILITIES
A) LOGIN
Ø
QC Explorer
Ø
Browse QC BIN url
Ø
Click “OK”
Ø
Do login by tester
Ø
Close welcome screen
Ø
Requirements components
Ø
Try to know responsible modules allocated by
test lead
B) WRITING
TEST SCENARIOS
After successful
login, corresponding test engineer can prepare test scenarios for responsible
modules on assigned test topics
Ø
Test plan component
Ø
Select test lead assigned testing topic or
subject
Ø
Test menu
Ø
New test
Ø
Select type as “Manual”
Ø
Type test scenario as test name
Ø
Click “OK”
Ø
Select Requirement coverage
Ø
Select requirement
Ø
Click “OK” after selection of corresponding
module as requirement
Ø
Follow above navigation to write scenarios for
all responsible modules on assigned testing topics or subjects
Exp#1: Validate LOGIN operation in windows XP
computer
Ø The
above scenario is related to LOGIN module’s O/S Compatibility or Platform
Compatibility Testing
Exp#2: Validate Money Transfer operation to other
bank accounts
Ø The
above scenario is related to MT module’s Inter System Testing
Exp#3: Validate Spelling of Labels in Mini Statement
Screen
Ø The
above scenario is related to MS module’s usability testing
Exp#4: Validate LOGIN operation by clicking “LOGIN”
button
Ø The
above scenario is related to Login module’s functional testing
NOTE: Every test scenario is traceable by module
name and testing topic
C) IMPLEMENTING
SCENARIOS INTO CASES
Ø Test
plan component
Ø Select
testing topic
Ø Select
scenario
Ø Details
Ø Type
details of test cases such as priority, test setup, test environment…..etc.,
Ø Design
steps
Ø Click
New Step Icon
Ø Enter
step description with cases (positive and negative by following black box
testing techniques)
Ø Click
“OK”
Ø Follow
above navigation to convert all scenarios into test cases documents
D) ATTACH
TEST DATA FILE
To execute test
cases on SUT, we need model test data or real test data, which can be prepared
in MS Excel and attach to QC
Ø Select
testing topic
Ø Select
test scenario
Ø Click
attachments
Ø Click
file attach icon
Ø Browse
path of the test data file
E) TEST
EXECUTION:
Test engineers
can review software builds given by developers and execute test cases in Smoke
Level, Real Level, Sanity Level, Regression Level and Post-mortem or Final
Regression Level Testing
In this
execution, test engineers can apply test cases on SUT by comparing expected
values and actual values on SUT. If the
expected value is matching as actual value, the test engineer must carry on
testing with further test cases, if the expected value is not matching with
actual value, the test engineer must stop testing and report the defects to DTT
Ø Test
Lab Component
Ø Test
Sets Menu
Ø New
Folder
Ø Enter
Project Name as Folder Name
Ø Test
Sets Menu
Ø New
Test Set (Test Set is also called as Batch, Group, Build, Chain, Oracle …etc.,)
Ø Enter
Batch name (Exp: TS_Login_FT)
Ø Click
“OK”
Ø Execution
grid
Ø Select
tests
Ø Select
previously prepared scenarios one by one into batch or set in an order
Ø Select
on scenario
Ø Click
“RUN”
Ø Select
one case and compare expected value with SUT’s actual value
Ø If
same continue further test cases, if not stop testing and report the defect to
DTT
F: DEFECT
REPORTING:
Ø Defects
Component
Ø New
Defect
Ø Fill
fields in defects report (Priority, Severity, Reoccurrence, Briefing about
defect, ….etc.,)
NOTE#1: In
general, test engineer can assign new defect to test lead. Test lead can review the defect and assign to
PM. Pam can discuss the defect with Team
Lead and assign to corresponding Developer
NOTE#2:
Generations of Test Management
1st Generation
|
MS Word for Scenarios
|
MS Excel for Test Cases & Test Data
|
MS Outlook for Defect Reporting & Tracking
|
2nd Generation
|
MS Word for Scenarios
|
MS Excel for Test Cases & Test Data
|
Jira/Bugzilla…etc.,
For Reporting & Tracking
|
3rd Generation
Current Generation
|
Quality Centre for Scenarios
|
Quality Centre for Test Cases & Test Data
|
Quality Centre for Defect Reporting & Tracking
|
NOTE: Quality Centre is
developed by Mercury Systems, Taken over by HP
|
|||
NOTE#3: Developers can login to QC to get the list of
defects detected by test engineers.
Hence, HP QC is a Complete Test Management Tool, which can work right
through from Test Scenarios to Defect Reporting and Tracking. HP QC is also very secured and reliable tool.
(END OF
QUALITY CENTRE)
No comments:
Post a Comment