Quality Center Basic Training

Quality Center Functionality and Features 29.3.2010

Soc Classification level 1 Nokia Siemens Networks

Presentation / Author / Date

Content
1) 2) 3) 4) 5) 6) 7) 8)
Quality Center User Interface Working in Quality Center Requirements Test Plan Test Lab Faults Filtering Reporting

Soc Classification level 2 Nokia Siemens Networks

Presentation / Author / Date

Demo 1: User Interface

How to log in
Where to get username

Navigation How to navigate between different modules, views and favourites

Refresh, Back and Forward buttons No Save button

Menus
Tools Help

When to log out

Soc Classification level 3 Nokia Siemens Networks

Presentation / Author / Date

Working in Quality Center

Requirements
Static Values
e.g. Feature, Feature Group, Responsibility, Priority, Req Type etc..

Test Plan
Static Values
e.g. Feature, Feature Group, Automation Type, Test Phase etc..

Test Lab
Dynamic Values
e.g. SW version, HW version, Platform used etc..

Faults
Run X Contains: -TC Static values -Dynamic values -Result information
(run status, date, time etc..)

Added on Reqs

Added on TCs

Added on TIs

Raise Fault

Requirement A

TCs covering requirement

Test Case A Test Case B Test Case C

Test Cases added into Test Set

Test Set Test Inst. A

Test Inst. B
Test Inst. C Fault A

Traceability
Soc Classification level 4 Nokia Siemens Networks Presentation / Author / Date

QC 10 Entity Model
1

Release
0-* 0-*

0-*
1 1 0-* 0-* 0-*

Cycle
0-*

Test Parameter 0-*

1 1 0-*

0-*

Test Set Folder

0-*

Requirement 0-*
0-* 0-* 0-* 0-* 0-*

Test Case

Design Step
0-*
0-*

Test Set

1 0-*

0-*

0-* 0-*

0-* 0-* 0-* 0-*

0-*

Test Instance
1 0-* 0-*

Fault Fault
0-*

Test case in Test Set is called Test Instance

Single Fault can be linked to many runs

0-*

Run
Soc Classification level 5 Nokia Siemens Networks Presentation / Author / Date

0-*

Run Step

Entities of Quality Center

Different database objects are called Entities in Quality Center (QC)
Requirement = Defines what system should do and define constraints for the system
under testing.

Test Case = a set conditions under which a tester will determine if requirements of an
application are met. A Test Case typically consists of Test Steps. Test Cases can be automated or manual. Folder of Test Cases is called Subject (in Test Plan Module)

Step = a single action a tester has to do to complete test Test Set = a collection of Test Cases. Can also be called an Execution Plan Test instance (previously known as Test Case in Test Set) In Quality Center when a Test Case is added to a Test Set,
it becomes a new entity with its own variables.

Test Run = an actual test event, where a step-by-step record of the test execution is
stored.

Fault = a bug or a defect which has been found during testing

Soc Classification level 6 Nokia Siemens Networks Presentation / Author / Date

NSN Usage Model

Harmonization is one part of NSN usage model User Groups Template user groups are used in NSN screenshots Data Fields
The single most important aspect in QC usage planning is the selection of field attributes to be used for data collection These fields can be used for data filtering and reporting purposes more easily than test asset tree structures or entity names

It is advised to use a shallow hierarchy

It is common to structure requirements by release / feature group / feature Information coded into the test set tree (folder structure, naming) cannot be easily used in reporting and also maintenance of the tree is a burden

Soc Classification level 7 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Lesson 1: Requirements

Soc Classification level 8 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

What is Requirements Module?

In Requirements module, you store the product requirements Requirements define what the service or product should do,
identifying and describing the characteristics and attributes Requirements are stored in hierarchical tree structure Requirements can be imported to QC from Microsoft Word or Microsoft Excel Integration to DOORS is available

Soc Classification level 9 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Demo 2: Requirements
In this demonstration you will be shown how to: Create a requirement structure Fill in Details Use the different views (Coverage view, Requirements Grid) Use the Zoom-in functionality Use of Edit menu Recycle Bin

Soc Classification level 10 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Exercise 1: Create a Requirement Structure

Soc Classification level 11 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Lesson 2: Test Plan

Soc Classification level 12 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

What is the Test Plan Module?

A centralized repository for all Test Cases
Test Case library Not a complete test plan!

In Test Plan module you create and manage A Folder structure (Test Plan Tree) Test Cases Manual Tests or Test Scripts Test Cases typically consist of Design Steps You can: Copy Test Cases between projects Copy data between Test Cases Import Test Cases from Word or Excel

Soc Classification level 13 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Call to Test

When creating Test Case A, you can fetch Steps from Test Case B by using the Call to Test-functionality
Useful when you have actions that are occurring frequently, such as
initialize terminal or login maneuvers

Note! There are some limitations when Call to Test functionality have been used, e.g. in reporting
The called steps will not appear in report

Soc Classification level 14 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Importing Test Assets

HP Mercury Add-ins: For importing Test Cases from Microsoft Word or Microsoft Excel to Quality Center
Download the add-in from Help -> Add-ins page Create a map between Excel columns and fields in QC
(You can also export Requirements and Faults to QC)

XML Import Tool: For importing Test Cases from XML files to QC
Install Import Tool Create a XML file including the Test Cases in specified format

Soc Classification level 15 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Demo 2.1: Test Plan

In this demonstration you will be shown how to: Browse Test Plan Tree Create a Folder structure View Test Cases and details Create a manual Test Case

Fill in the required fields Add a description text Add steps Add attachments Call to Test functionality

Soc Classification level 16 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Exercise 2.1: Create a Test Plan Structure, Add a Test Case

Soc Classification level 17 Nokia Siemens Networks

Presentation / Author / Date

Exercise 2.2: Call to Test Functionality

Soc Classification level 18 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Demo 2.3: Requirement Test Case Link

After you have created your Requirements and Test Cases, it is time to create a link between these two entities
This is called covering Requirements with Test Cases.

Linking can be done

in two modules: In Test Plan, linking a single Test Case to one or many Requirements In Requirements, linking a single Requirement to one or many Test
Cases manually or by filtering

You can use Requirements module for planning your testing

Test Sets can be built based on Requirements. Requirements are the basis of reporting in Quality Center.
Soc Classification level 19 Nokia Siemens Networks Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Exercise 2.3: Link a Test Case to a Requirement

Soc Classification level 20 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Lesson 3: Test Lab

Soc Classification level 21 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

What is the Test Lab Module?

In Test Lab you: Create a folder structure (Test Sets Tree) Create Test Sets
A Test Set is a collection of Test Instances Dynamic values are put into Test Set fields

Add Test Instances to be executed Create Test Runs for the Test Instances Add and link Faults during Runs A Test Set enables you to plan the test execution
Testing against your Requirements

A Test Set can include both manual and automated tests

Soc Classification level 22 Nokia Siemens Networks Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Notes about Test Sets

Test Sets should have a unique name!
Otherwise QC will calculate results together in reports Create and organize Test Sets according to your needs E.g. by software build, software version, test phase, feature, milestone, tester

You can use filters when adding Test Instances to the Test Set You can create the Test Set from Requirements Test Coverage. Use an existing Test Set as template for a new one.
Always remember to check that the dynamic values are correct Also check if someone has added new tests that need to be run for that
particular assembly

SW Build and Release are mandatory fields in Test Set

Soc Classification level 23 Nokia Siemens Networks

Presentation / Author / Date

An Example of Field Value Inheritance

Click! Click! Click!

Test Case Feature Group RF Feature TX Test Type Auto

Test Set Product FlexiEDGE Release Alpha SW Build 0102

Test Instance Feature Group RF Feature TX Test Type Auto Product FlexiEDGE Release Alpha SW Build 0102

Run Feature Group RF Feature TX Test Type Auto Product FlexiEDGE Release Alpha SW Build 0102

Fault Feature Group RF TX Feature Auto Test Type Product FlexiEDGE Release Alpha SW Build 0102

1. Create a Test Case, add static values 2. Create a Test Set, add dynamic values to Details 3. Include Test Case into Test Set (=Test Instance) 4. Update the field values from Test Set to Test Instances 5. Run the Test 6. If the Run fails, create a Fault
Soc Classification level 24 Nokia Siemens Networks

TEST FAILS X

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Demo 3.1: Test Set Planning

Creating a Test Lab folder structure Creating a Test Set Setting the Test Set required fields Adjusting the Execution Grid columns Adding Test Instances to a Test Set Replacing field values in Execution Grid Updating values from Test Set to Test Instance fields
by pressing

Update Test Instances values from Test Set properties Details - button
Soc Classification level 25 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Exercise 3.1: Test Set Planning

Soc Classification level 26 Nokia Siemens Networks

Presentation / Author / Date

Test case execution states 1/3

NOTE! These are mandatory in NSN level (no tailoring allowed in BU/BLs) Passed Test case is passed according to defined pass / fail criteria Failed Test case is failed according to defined pass / fail criteria No Run Initial state for a test case. Test case has not been executed yet. Not Completed Test case execution has been started, but not yet completed (paused) for some reason. N/A (Not Applicable) Test case is not applicable or relevant to be executed or has become obsolete for some reason. For example if the originally planned feature is removed from the program content. Reason for N/A state should be written in test case report and program / project status reports

Soc Classification level 27 Nokia Siemens Networks

Presentation / Author / Date

Test case execution states 2/3

Not Analyzed Test case has been executed, but the results are not yet completely analyzed Recommended to be used in situation where complete analysis is not done during same day than execution or if otherwise instructed by the program. Use of this state gives better visibility to test execution progress. The reason might be that the analysis is very time consuming and/or verdict of test case is unclear (no enough information is available currently for complete analysis). Blocked Test case is not possible to be executed at the moment, due to some hindering technical reason. These might be for example test environment problems (tools, scripts, laboratory environment) or defect(s) in the system under test. Reason for blocking should be written in test case report and program / project status reports

Soc Classification level 28 Nokia Siemens Networks

Presentation / Author / Date

Test case execution states 3/3

Postponed Test case is moved to be executed at later program phase than originally planned Allowed to be used if originally planned test execution is moved to later program phase (e.g. if originally planned content is moved to later program phase, for example after P7 when customer pilots starts) Reason for postponing should be written in test case report and program / project status reports Use of this state requires approval from program / project management

Soc Classification level 29 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Demo 3.2: Executing Tests

Executing a single manual test using the Manual Runner Selecting multiple tests and running them with Manual Runner Adding Faults during a Manual Test Run Fast Run (How to add a fault) Checking the Test Instance Properties Filtering in the Execution Grid

Soc Classification level 30 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Exercise 3.2: Executing Tests

Soc Classification level 31 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Lesson 4: Faults

Soc Classification level 32 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

What is Faults Module?

Faults module contain the bugs / faults / errors that were
found during testing
Faults can be added any time Quality Center offers many ways to link Faults. Some of them might not
be needed in your project.

In NSNs configuration, Fault objects inherit the field values

from Runs
This helps in reporting and also eases the work of tester
Tester does not have to fill in all the field values while adding Faults

There will be an integration to NewGen/MoTTo system from

Quality Centers Faults module

Soc Classification level 33 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Faults Linkage in Quality Center

Test Set

Run Step

Run

Test Instance Test Requirement

When you add a Fault, QC creates an indirect link to other

entities in the chain
A one-way chain, so e.g. if Fault is added to a Run,
Run Steps are not linked.

You can manage Fault links from the Linked Faults dialog In Faults module you can see all the entities linked to
a certain Fault by clicking Linked Entities

Soc Classification level 34 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Demo 4.1: Faults

Adding a Fault during Manual Run Viewing linked entities in Faults module Viewing linked Faults in Test Lab Adding attachments to Fault Using Grid filters in Faults module

Soc Classification level 35 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Exercise 4.1: Fault Tracking

Soc Classification level 36 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Lesson 5: Filtering Data

Soc Classification level 37 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Notes About Filtering

You can use filtering in all four modules and views Filtering is really easy in Quality Centers Grid views Use logical expressions in order to combine different
conditions Also cross-filtering between modules is possible
For example:
Show me all approved Test Cases (in Test Plan) that have links to Faults that are detected by me

Advanced filters
In Test Plan

Soc Classification level 38 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Saving as Favorites
Filters and views can be saved as favorites
In Requirements, Test Plan
and Faults modules: Favorites -menu

In Test Lab module

there is no favorites

Soc Classification level 39 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Demo 5: Filtering Data

Filtering in Grid views Using Advanced Filter (cross-filter) Using logical expressions Filtering in Faults module Sorting items in Grid view Grouping Grid records Saving filters as favorites

Soc Classification level 40 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Exercise 5: Filtering Data

Soc Classification level 41 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Lesson 6: Reporting and Analysis

Soc Classification level 42 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Notes About Reporting

Quality Center offers four tools for reporting purposes
Analysis menu in each module
For creating textual reports or graphs based on field values Can be saved as Favorites or in HTML format With Graph Wizard you can create a graph at once

Live Analysis on folder level

You can create two graphs side-by-side from folder contents Updates on-the-fly if you change focus to a different folder

Document Generator for generating project level Word documents

You can get all project data into a single document Can contain pre-defined graphs and Attachments
Snapshot of the current situation

Dashboard module
Soc Classification level 43 Nokia Siemens Networks Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Demo 6: Reporting and Analysis

Analysis menu: Graphs and Reports

Viewing and editing reports Configure Reports & Sub-Reports Customize Fields Viewing and editing Graphs Drill-down results Adding reports and graphs to Favorites Graph Wizard

Live Analysis Document Generator

Generating reports Adding to Favorites

Soc Classification level 44 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Exercise 6: Reporting and Analysis

Soc Classification level 45 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Limitation in Requirement Coverage Information

Quality Center always shows the last status of
Test Execution

Coverage data of the Requirements show only the result of the last run of a Test Case with no capability of filtering on Run parameters

Status of a Test Case in the Test Plan it only shows the result of the last run of the Test Case in any Test Set

Soc Classification level 46 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Limitation in Requirement Coverage Information

Requirements

Test Plan
Pass
Test Case. 1

Test Lab
Prod. 1 Test Set. 1

Pass
Test Case. 1

Pass
Test Case. 2

Pass Prod. 1 Req. 1 Pass Pass

Test Case. 2

Test Case. 1 Prod. 2 Test Set. 2 Test Case. 2 Prod. 2

Pass Req. 2 Pass

Test Case. 3 Test Case. 3

Prod. 3 Req. 3

Prod. 3 Test Set. 3

Test Case. 3

Soc Classification level 47 Nokia Siemens Networks

Presentation / Author / Date

Requirements

Test Plan

Test Lab

Faults

Filtering

Reporting

Limitation in Requirement Coverage Information

Requirements

Test Plan
Pass Fail
Test Case. 1

Test Lab
Prod. 1 Test Set. 1

Pass
Test Case. 1

Pass
Test Case. 2

Pass Fail Prod. 1 Req. 1 Pass Pass

Test Case. 2

Fail
Test Case. 1 Prod. 2 Test Set. 2

Pass
Test Case. 2

Prod. 2

Pass Fail Req. 2 Pass

Fail

Fail Test Case. 3

Fail
Test Case. 3

Prod. 3 Fail Req. 3

Prod. 3 Test Set. 3

Test Case. 3

Soc Classification level 48 Nokia Siemens Networks

Presentation / Author / Date

Questions?

Soc Classification level 49 Nokia Siemens Networks

Presentation / Author / Date

Quality Center Basic Training

Please visit the NSN QC Wiki at
https://confluence.inside.nokiasiemensnetworks.com/display/Home

Soc Classification level 50 Nokia Siemens Networks

Presentation / Author / Date