Quality Center 9.

2 Connecting the
Dots

Mary Larson August 2009

Presentation Agenda
• How the Quality Center tabs are connected
• • • • Requirements Test Plan Test Lab Defects

• Demonstrate how to bridge data gaps
• Going From Test Cases to Test Sets

• Verifying traceability and test coverage
• Best practices to ensure compliance
INTERNAL

1. Quality Center Integration
Requirements

Defect

Test Plan

Test Lab
INTERNAL

Quality Center Tab Integration
Requirements
• Go to Test in Test Set • Associate a Requirement • Report: Requirements Coverage

Test Plan
• Go to Test in Test Set • Associated Defects • Report: Tests with Associated Defects

Test Lab
• • • • Go to Test in Test Plan Tree Associated Defects Report: Cross Test Set with Tests Report Defect link from Steps of Run window

Defects • Associated Test • Report: Defects with Associated Tests and Runs • Favorite: _Defect with Test Steps
INTERNAL

Test Case to Test Sets and Defects
Right-Click on Test Case to go to Test in Test Set “go to” Associated Defects

INTERNAL

Quality Center Standard Reports
Tests with Linked Defects

INTERNAL

Tests with Linked Defects

INTERNAL

Defect to: Test Case in Test Set

INTERNAL

Defect to: Associated Test
Right-Click on Defect to go to Associated Test (Test Set run where detected)

INTERNAL

Quality Center: Sub-Reports

INTERNAL

Quality Center: Advanced Reporting

INTERNAL

Quality Center: Advanced Reporting

INTERNAL

Connecting Test Plan and Test Lab execution? • How do we plan for test
• Building a bridge” from the test plan to test lab tabs • Need to plan where and when test cases will be run • What’s available to assist us on the Test Plan tab?
     Test Set/Execution Cycle (40 characters) Test Stage and Test Type Subject Tree (folder structure) Other Info 1-4 fields Additional fields?

• Are you using any of these fields to “bridge tab gaps” and assist with Test Set planning? • Which fields are you using?
INTERNAL

Test Cases used in Multiple Test Sets Cycle field. Use the Test Set/Execution
• Determine Test Set naming conventions. • Determine “short names” for Test Set/Exec Cycle. • Use comma “ , “ to separate test set “short names”.

Example:

• SM_ST_Test01 will be run in multiple Test Sets.
    Test Set names = SM06_ST_01 – SM06_ST_xx Short name for test sets = ST01 - STxx TS/EC = ST01,ST04,ST05,ST08 Use Filter when building Test Sets, e.g. *ST01*

INTERNAL

Test Cases in Test Grid View

INTERNAL

Filtering Test Cases in Test Lab

INTERNAL

3. Test Coverage and Quality Center
Paradigm Shift:
• From a test coverage perspective, there are two pieces: planning and execution • If you plan without executing, you’ve only completed half the task • You must follow-through from test planning and execute the tests

INTERNAL

Ensuring Traceability
Use the following Requirements Tab Favorites
• _Req to Test Case Traceability - Summary • _Req to Test Case Traceability - Detailed
 Note: Customize the display to meet your needs

INTERNAL

Ensuring Traceability
Generate Req to Test Case Traceability Detailed  Make sure ALL requirements are prioritized and tested  This can be found on the Requirements Tab in Quality Center

INTERNAL

Ensuring Traceability
Recommendations:
• Rqmt. ID – store only ONE requirement ID.
 Use Other Info 1-4 fields for additional rqmts.  Follow this or traceability will be VERY difficult.

• Use Continue Manual Run option
 Reduces number of bogus “Not Completed” runs.  Return to add a defect – creates a link to the run.

• Flag tests for Regression and Smoke Testing
 Review tests that produced defects for regression.
INTERNAL