Anda di halaman 1dari 36

Quality Center

Training Courseware

By

Nagarajan

1
Table of contents

INTRODUCTION 03

SITE ADMINISTRATOR FEATURES 04

PROJECT ADMINISTRATOR FEATURES 08

PROJECT USER FEATURES 09

REQUIREMENTS MANAGEMENT 13

TEST PLAN 15

TEST LAB 19

DEFECT MANAGEMENT 22

TOOL BAR FOR DEFECTS 22

REPORTS AND GRAPHS 24

2
INTRODUCTION

Quality Center, a Web enabled test management solution helps organizations to deploy
high-quality applications more quickly and effectively. It has four basic modules -Requirements, Test
Plan, Test Lab and Defects. These modules are integrated to allow a smooth information flow
between various testing stages.

When a large team executes a project from various locations at various time zones, this kind of
a central management tool will reduce lot of human communication gaps and errors. Issue tracking
will be made easy. Quality Center is a central point of control for storing all information about
application requirements, tests and defects in a central repository of testing projects.

The main Features of Quality Center are:


• Manage Domains
• Manage Projects
• Manage users and roles
• Manage Requirements
• Manage Tests
• Manage Test Sets and Runs
• Manage Defects
• Generate Reports and Graphs
• Status based email alerts and notifications
• Customizable fields and history maintenance

3
QUALITY CENTER MAIN PAGE
When you install Quality Center, the installation program creates a repository.
The repository is a directory that stores Quality Center domains and Site Administrator data.
It contains the following subdirectories:

Quality Center: This directory stores Quality Center domains.


It includes a default domain and may also include user-defined domains.
Each domain contains Quality Center projects.

Site Administrator: This directory stores the Site Administrator data in the DomsInfo
subdirectory which contains StyleSheets and Templates

• StyleSheets, a subdirectory for storing global style sheets.


• Templates, a subdirectory for storing database templates used when creating new projects.

SITE ADMINISTRATOR FEATURES

• Site admin is the super user of the system

4
• Can create/delete Domains
• Can create/delete/rename Projects
• Each project is a separate set of tables
• Can create users at global level
• Can modify the license details
• License files are supplied by Mercury Interactive
• Can modify the server locations
• Can set global configuration settings

SITE ADMINISTRATOR

5
SITE ADMINISTRATOR MAIN PAGE

6
CREATION OF DOMAIN

7
8
CREATION OF PROJECT

9
CREATION OF USERS

10
Assigning Users to the project

11
DETAILS OF THE SERVER

The step to be done in any project is to set up the project, user groups, and users and other
look up values. This can be created by site admin and project admin users.

12
13
PROJECT ADMINISTRATOR FEATURES

• First step is to customize project specific codes (Customize)


• Can create different user groups (Setup User Groups)
• Each user group can be given access rights for different portfolio (Permissions)
• Access rights are mainly add, modify, delete, view and administer
• Access rights can be given right at the field level of every module
• One can define access rights for add/modify/delete test assets
• Quality Center provides modification rights, to field by field level
• Add users from global user list and map them to user groups (setup users)
• Can customize project entities, by altering attributes of system defined fields and user defined
fields – label, history and Masked can be modified as we need
• User defined fields can be string, date, or list of values

14
• Can maintain different list of values for priority, severity, version, status codes etc
• Can configure email alert options

CUSTOMIZATION WINDOW

PROJECT USER FEATURES

• Each project User will be shown with menu items, that are enabled based on
the access rights
• Each user is attached to one or more user groups and inherits all the access
rights of those groups
• Workflow is defined internally to take the user through specific process steps
• Email notifications are made to alert and notify the users
• Each user can access one of the four available options – Requirement, Plan,
Test Lab, Defects
• Search and filter is available across all options

15
• Standard reports are built-in with the product
• Users can customize required graphs as and when needed
• Reports can be saved in HTML or text formats
• The workflow is initially set by the project admin and every user goes through
this workflow based on access rights

MAPPING THE GLOBAL USERS TO THE PROJECT

16
CREATION OF DIFFERENT USER GROUPS AND
GIVE PERMISSIONS FOR DIFFERENT PORTFOLIO

PRIVILEGE RIGHTS FOR USERS TO ACCESS MODULE

17
EACH ENTITY CONTAINS SYSTEM FIELDS AND USER-DEFINED FIELDS

1) System fields are Quality Center default fields. You cannot add or delete
system fields. You can only modify system fields.

2) User fields are fields that you can define and include in a Quality Center
project to customize for your specific project needs. You can add, modify, and
delete user-defined fields.

CREATION OF PROJECT LISTS

18
CONFIGURE MAIL
Quality Center enables you to automatically notify users via e-mail, when changes are
made to specified defect fields

SET TRACEBILITY NOTIFICATION RULES

Instructs Quality Center to create alerts and send e-mails to notify those responsible
when changes occur in the project

19
MODULES OF QUALITY CENTER

REQUIREMENTS MANAGEMENT

Requirements-based testing keeps the testing effort on track and measures the
application against business-user needs. Quality Center Requirements Manager links test cases to
application functional requirements, ensuring traceability throughout the testing process. Quality
Center enables the user to easily see what percentage of the application functional requirements are
covered by tests, how many of these tests have been run, and how many have passed or failed.
• All project requirements are added in a tree like fashion, arranged hierarchically
• We can maintain parent-child relationship of requirements
• Requirements ID can be made auto generated
• Data entry happens like we enter in spreadsheets
• Detailed description, priority, type, attachment etc can be provided and history will be
maintained
• Person in-charge to review the requirements can modify status accordingly
• Requirements can be mapped to test cases through coverage view
• Required columns can be made visible

20
TOOLBAR OF REQUIREMENT MODULE

DOCUMENT VIEW

COVERAGE ANALYSIS VIEW

21
TEST PLAN

Planning Tests: Based on the requirements, testers can start building the test plan and
designing the actual tests. Test plans can be created in Quality Center or imported from Microsoft
Word or Excel. Quality Center supports manual and automated tests, as well as a transition to
automation. By maintaining all test planning information in a central repository, team members can
easily reuse entire test plans or individual test cases for future application releases.

• Create Test folders (scenarios) in tree fashion and attach test cases at leaf level nodes
• One can view in tree mode or grid mode
• Test folders can have description and attachments
• Test cases will have detailed description, steps, priority, attachments, author
• Name, scripts if automated and its associated requirement mapping
• Test steps can be reordered
• Required columns can be made visible
• Based on settings, history will be maintained when test cases are modified
• Test case can be manual or automated tests
• TD test case can be mapped to WinRunner, LoadRunner, Visual API, Astra Load test or
System tests
• Test cases can be separately emailed
• Standard reports and graphs are available as part of Analysis

TOOL BAR FOR TEST PLAN

22
TEST DETAILS VIEWED THROUGH TEST PLAN TREE

23
TEST DETAILS VIEWED THROUGH TEST GRID

TEST PLAN- DETAILS STEPS

24
TEST PLAN- TEST SCRIPT

TEST PLAN- ATTACHMENTS

25
TEST PLAN- REQUIREMENTS COVERAGE

The Requirement Coverage tab enables you to define requirements coverage by linking your
tests to requirements and also used to identify whether any requirement are missed.
The tab provides a list of all the testing requirements defined in the Requirements module,
and enables you to map the specific requirements that are covered by the currently selected test to
that test.

TEST LAB

Quality Center Test Lab Manager allows scheduled tests to run unattended, overnight
or when the system is in least demand for other resources. By defining dependencies between tests,
users can realistically emulate real-life business processes, while making it easier to maintain and
reuse the tests.
• One can create test sets (test rounds) and associate test cases to that test set and provide
planned start and end dates
• Using Execution Grid, one can map the test cases to the test set

26
• One can assign planned execution date, tester, and host machine for that test as part of test
run
• Testers can feed the test run details (actual results) as part of test run for each test step along
with pass or fail status
• Automated tests will launch the test automation tool and run the associated test script
• Test execution flow can document and run automated test suites
• Standard reports and graphs are available

TOOL BAR FOR TEST LAB

27
TEST LAB DETAILS VIEW THROUGH EXECUTION GRID

TEST LAB DETAILS VIEW THROUGH EXECUTION FLOW

28
TEST LAB DETAILS VIEW THROUGH TEST SET PROPERTIES

DEFECT MANAGEMENT

Quality Center Defect Manager supports the entire defect life cycle - from initial problem
detection through fixing the defect and verifying the fix. This ensures that no defect is overlooked or

29
closed before it has been addressed. Before any new defect is submitted, Quality Center checks the
database for similar defects, minimizing duplicate defects and eliminating the need for manual
checking.

• Add defects by providing description, priority, severity, attachments, version


• code, and status code
• Based on workflow as per defined process, the defect will be taken through the cycle – Open,
Fix, Retest, Close
• Project admin must configure the status change permissions to define bug work flow
• Email notifications happen as and when certain fields are modified (as defined by project
admin)
• Detailed bug history is maintained
• Selective emailing as well as standard reporting are available
• Display of required columns and filtered display are also available
• Bugs can be saved in html, excel, word or text files

TOOL BAR FOR DEFECTS

30
DEFECT DETAILS

REPORTS AND GRAPHS

31
The testing process generates large amounts of data. Quality Center customizable
graphs and reports help users analyze the data.
• As part of Analysis, we can generate reports and graphs on requirements, test plans/cases,
test sets and defects
• We can generate custom reports by providing filter, sort and group conditions
• Graphs can be viewed in pie chart or bar chart
• Graphs can be configured based on sum or count of key fields

REPORTS

GRAPHS

32
GRAPH WIZARD

33
REQUIREMENT REPORT

REQUIREMENT GRAPHS (BAR CHART)

34
REQUIREMENT GRAPHS (PIE CHART)

REQUIREMENT GRAPHS (DATA GRID)

35
DEFECTS - REPORT

DEFECTS - GRAPHS`

36

Anda mungkin juga menyukai