USING QUALITY CENTER

Author:

Paulina Contreras

Creation Date: 02-MAY-2014

Last Updated:

13-MAY-2014

Version:

1.0

Document Control
Change Record
Date

Author

Version

Change Reference

13-MAY-2014

Paulina Contreras

1.0

No Previous Document

Reviewers

Name

Position

Distribution

Copy
No.

Name

Location

1
2
3
4

Library Master

Project Library
Project Manager

Note To Holders:
If you receive an electronic copy of this document and print it out,
please write your name on the equivalent of the cover page, for
document control purposes.
If you receive a hard copy of this document, please write your name
on the front cover, for document control purposes.

Using Quality Center.doc

pg. ii

Table of Contents
Document Control............................................................................. ii
Application Lifecycle Management Roadmap....................................2
Requirements.................................................................................... 3
Requirements Details...................................................................3
Test Coverage.............................................................................. 4
Test Plan............................................................................................ 5
Test Cases.................................................................................... 5
Test Scenarios................................................................................ 6
Requirements Coverage...............................................................6
Test Lab............................................................................................. 6
Running Tests............................................................................... 7
Defects........................................................................................ 9
Entering Defects..........................................................................9
Linking Defects..........................................................................10
Appendix A Flowchart of Defect Process in Quality Center...........11

Using Quality Center.doc

pg. iii

Application Lifecycle Management Roadmap

In Quality Center, also known as Application Lifecycle Management (ALM), we use this
roadmap for a project:

Phase

Description

Requiremen
t
Specification
s

Define requirements to meet your business and testing needs. You can
manage the requirements and conduct multi-dimensional traceability
between requirements, tests, and defects, across multiple releases and
cycles. ALM provides real-time visibility of requirements coverage and
associated defects to evale quality and business risk.

Test
Planning

Based on the project requirements, you can build test plans and design
tests. ALM provides a repository for both manual and automated tests.

Test
Execution

Create a subset of the tests in your project designed to achieve specific test
goals. ALM supports functional, regression, performance, and advanced
testing. Execute scheduled tests to diagnose and resolve problems.

Defect
Tracking

Submit defects and track their repair progress. Analyzing defects and defect
trends helps you make effective "go/no-go" decisions. ALM supports the
entire defect lifecycle - from initial problem detection through fixing the
defect and verifying the fix.

Using Quality Center.doc

pg. iv

Requirements
Requirements describe in detail what needs to be solved or achieved to meet the
objectives of your application under development. The Requirements module enables you
to define, manage and track requirements at all stages of the application lifecycle
management. We start with the process flows to enter basic requirements. Requirements
are not system specific.

Requirements Details
Enter detailed information for requirements. You can use the fields ALM provides and add
your own. Click on the link for the Req ID. Since we have not run any of our test scripts
yet, the Direct Cover Status field has a value of No Run.

Using Quality Center.doc

pg. v

Test Coverage
It is essential that the tests in your test plan meet your original requirements. To keep
track of the relationship between your requirements and tests, you add links between
them. Test coverage assists you in assessing the scope of testing to achieve all of the
requirements, and the impact of a change in the test or requirement. A test can cover
more than one requirement.

Using Quality Center.doc

pg. vi

Test Plan
Developing a clear and concise test plan is fundamental to successful application testing.
A good test plan enables you to assess the quality of your application at any point in the
application management process. Outline a strategy for achieving your requirements, as
defined in the Requirements module.

Test Cases
Test scripts contain detailed steps on how to execute a test and evale the results.

Test Scenarios

ALM also enables you to use the same test to test different Test Scenarios. Each Test
Scenario uses a different set of data. Use the Test Configurations tab to enter the data for
the Test Scenarios. For example, we may execute this test script for two different test
scenarios: Creating a new strategic customer and creating a new non-strategic customer.

Using Quality Center.doc

pg. vii

Requirements Coverage
In the Test Plan module, you create requirements coverage by linking tests to a
requirement just like in the Requirements Module. Requirement coverage assists you in
assessing the impact of a change in a requirement. A test can cover more than one
requirement.

Test Lab
Test Lab is where you run your test scripts. You can combine test scripts together into a
test set, but each test script can be in its own test set. Test Lab also has functionality to
run automated tests. Test sets can contain both manual test and automated tests. For
example, suppose we want a tester to execute all the test scenarios for the Create new
customer test which includes a strategic and non-strategic customer. We can combine the
test scenarios into one test set. That way, only when the tester runs both scenarios in the
one test set do they indicate the entire test set is passed.

Running Tests
After establishing test sets, select the Run Test Set icon in Test Lab to run a test.

Using Quality Center.doc

pg. viii

Click Begin Run to start the test

Enter the actual results and indicate whether a step passes, fails, etc. You can also
change the test script while running the test by inserting, removing, or changing the
steps.

Using Quality Center.doc

pg. ix

You can always stop a test, pause a test, start from the beginning of the current test, and
start from the beginning of a new test run.
When all of the steps of a test are passed, ALM updates the status of the test script to
Passed. When all of the test scripts identified to cover requirements are passed , we
update the status of the requirement to Passed. When all of the requirments are
passed, the test plan is complete and we proceed to the Installation phase.

Defects
Locating and repairing application defects efficiently is essential to the development
process.
You use the Defects module to:

Create application defects for an ALM project.

Track defects until application developers and testers determine that the defects
are resolved.
Defects inform members of the application development and quality assurance teams of
new defects discovered by other members. As you monitor the progress of defect repair,
you update the information in your project. The QA Team will work with you to track
defect progress.

Entering Defects
You can enter a new defect while you are running a test, or later. Here is an example of
entering a defect during a test run.

Using Quality Center.doc

pg. x

Linking Defects
It is important to link defects to test scripts so other team members can use the test script
for retesting. If you create a defect while running a test, ALM automatically links the
defect to the test script. If you create a defect later, you must manually link the defect to
the test script.

Using Quality Center.doc

pg. xi

After creating the defect, link it to the appropriate test script

Using Quality Center.doc

pg. xii

Appendix A Flowchart of Defect Process in Quality Center

Using Quality Center.doc

pg. xiii