03_Quality Center Functionality and Features

8/2/2019 03_Quality Center Functionality and Features

1/50

Soc Classification level

1 Nokia Siemens Networks Presentation / Author / Date

Quality Center Basic TrainingQuality Center Functionality and Features

29.3.2010


2/50



Content

1) Quality Center User Interface

2) Working in Quality Center

3) Requirements

4) Test Plan

5) Test Lab6) Faults

7) Filtering

8) Reporting


3/50



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


4/50



Working in Quality Center

Requirements Test Plan Test Lab Faults

Requirement A

Test Case A

Test Case B

Test Case C

Run XContains:

-TC Static values-Dynamic values

-Result information(run status, date, time etc..)

TCs covering

requirementTest Inst. A

Test Inst. B

Test Set

Test Casesadded intoTest Set

Test Inst. C

Fault A

R

aiseFault

Addedon

TCs

Addedon TIs

Addedon

Reqs

Static Valuese.g. Feature, FeatureGroup, Responsibility,Priority, Req Type etc..

Traceability

Static Valuese.g. Feature, Feature

Group, Automation Type,Test Phase etc..

Dynamic Valuese.g. SW version, HW

version, Platform used etc..


5/50



0-*

Test

Instance0-*

0-*

0-*

0-*

Test Case

1

10-*

0-*

DesignStep

Run

1

0-*

1

Run

Step

0-*

0-*

0-*

0

-*

0-*

0-*

Fault

0-*

Test Set1

0-*

0-*

0-*

0-*

0-*

0-*

0-*

0-*

Single Fault can belinked to many runs

Test case in TestSet is called Test

Instance

Release

Cycle

Requirement

Fault

Test SetFolder

0-* 0-*

0-* 0-*

1 0-*

1

1

0-*0-*

TestParameter 0-*

1

1

1

0-* 0-*

QC 10 Entity Model


6/50



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 anapplication 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 isstored.

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


7/50



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 selectionof field attributes to be used for data collection

These fields can be used for data filtering and reporting purposes moreeasily 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) cannotbe easily used in reporting and also maintenance of the tree is a burden


8/50



Lesson 1:Requirements

ReportingFilteringFaultsTest LabTest PlanRequirements


9/50



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 orMicrosoft Excel

Integration to DOORS is available



10/50



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


R iFil iF lT L bT PlR i


11/50



Exercise 1:Create a Requirement Structure


R tiFilt iF ltT t L bT t PlR i t


12/50



Lesson 2:Test Plan


R tiFilt iF ltT t L bT t PlR i t


13/50



What is the Test Plan Module?

A centralized repository for all Test Cases

Test Case library

Not a complete test plan!

In Test Planmodule 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




14/50



Call to Test

When creating Test Case A, you can fetch Steps from

Test Case Bby 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 Testfunctionality have been used, e.g. in reporting The called steps will not appear in report


ReportingFilteringFaultsTest Lab

Test PlanRequirements


15/50



Importing Test Assets

HP Mercury Add-ins:

For importing Test Cases from Microsoft Word orMicrosoft Excel to Quality Center

Download the add-in from Help ->Add-inspage

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


http://qc.inside.nokiasiemensnetworks.com/qcbin/addins.htmlhttps://confluence.inside.nokiasiemensnetworks.com/display/QC90/XML+Import+toolhttps://confluence.inside.nokiasiemensnetworks.com/display/QC90/XML+Import+toolhttp://qc.inside.nokiasiemensnetworks.com/qcbin/addins.htmlhttp://qc.inside.nokiasiemensnetworks.com/qcbin/addins.htmlhttp://qc.inside.nokiasiemensnetworks.com/qcbin/addins.html


16/50



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




17/50



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



18/50



Exercise 2.2:Call to Test Functionality



19/50



Demo 2.3:RequirementTest 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 TestCases

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.




20/50



Exercise 2.3:Link a Test Case to a Requirement




21/50



Lesson 3:Test Lab

p ggq



22/50



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

p ggq



23/50



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 thatparticular assembly

SW Build and Release are mandatory fields in Test Set

p ggq


24/50



Test Case Test Set Test Instance Fault

Feature GroupFeatureTest Type


ProductReleaseSW Build




Run



Click!

An Example of Field Value Inheritance

Click! Click!

RFTXAuto

FlexiEDGEAlpha0102

RFTXAuto

RFTXAuto

FlexiEDGEAlpha0102

FlexiEDGEAlpha0102

RFTXAuto

FlexiEDGEAlpha0102

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

TEST FAILSX



25/50



Update Test Instances values from Test Set properties Details- button

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 fieldsby pressing



26/50



Exercise 3.1:Test Set Planning


27/50



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 criteriaFailed

Test case is failed according to defined pass / fail criteriaNo 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 isremoved from the program content. Reason for N/A state should be written in test case report and program /project status reports


28/50




Not Analyzed Test case has been executed, but the results are not yet completelyanalyzed

Recommended to be used in situation where complete analysis is notdone during same day than execution or if otherwise instructed by theprogram. Use of this state gives better visibility to test execution progress.

The reason might be that the analysis is very time consuming and/orverdict of test case is unclear (no enough information is availablecurrently for complete analysis).

Blocked Test case is not possible to be executed at the moment, due to somehindering technical reason. These might be for example test environmentproblems (tools, scripts, laboratory environment) or defect(s) in thesystem under test.

Reason for blocking should be written in test case report and program /project status reports


29/50




Postponed Test case is moved to be executed at later program phase than originallyplanned

Allowed to be used if originally planned test execution is moved to laterprogram phase (e.g. if originally planned content is moved to laterprogram phase, for example after P7 when customer pilots starts)

Reason for postponing should be written in test case report andprogram / project status reports

Use of this state requires approval from program / project management



30/50



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



31/50



Exercise 3.2:Executing Tests



32/50



Lesson 4:Faults



33/50



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 notbe needed in your project.

In NSNs configuration, Fault objects inherit the field valuesfrom 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 fromQuality Centers Faults module

F l Li k i Q li CReportingFilteringFaultsTest LabTest PlanRequirements


34/50



Faults Linkage in Quality Center

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 Faultsmodule you can see all the entities linked toa certain Fault by clicking Linked Entities

Run Step Run Test Instance

Test Set

RequirementTest

D 4 1ReportingFilteringFaultsTest LabTest PlanRequirements


35/50

Soc Classification level35 Nokia Siemens Networks Presentation / Author / Date

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

E i 4 1ReportingFilteringFaultsTest LabTest PlanRequirements


36/50


Exercise 4.1:Fault Tracking

L 5ReportingFilteringFaultsTest LabTest PlanRequirements


37/50


Lesson 5:Filtering Data

N t Ab t Filt iReportingFilteringFaultsTest LabTest PlanRequirements


38/50


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 differentconditions

Also cross-filtering between modules is possible For example:

Show me all approved Test Cases (in Test Plan) that have links to Faultsthat are detected by me

Advanced filters In Test Plan

S i F itReportingFilteringFaultsTest LabTest PlanRequirements


39/50


Saving as Favorites Filters and views can be saved as favorites

In Requirements, Test Planand Faultsmodules:Favorites -menu

In Test Labmodulethere is no favorites

D 5ReportingFilteringFaultsTest LabTest PlanRequirements


40/50


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

E i 5ReportingFilteringFaultsTest LabTest PlanRequirements


41/50


Exercise 5:Filtering Data

Lesson 6ReportingFilteringFaultsTest LabTest PlanRequirements


42/50


Lesson 6:Reporting and Analysis

Notes About ReportingReportingFilteringFaultsTest LabTest PlanRequirements


43/50


Notes About Reporting

Quality Center offers four tools for reporting purposes

Analysismenu 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 Analysison 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 Generatorfor 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

Dashboardmodule

Demo 6:ReportingFilteringFaultsTest LabTest PlanRequirements


44/50


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

Exercise 6:ReportingFilteringFaultsTest LabTest PlanRequirements


45/50


Exercise 6:Reporting and Analysis

Limitation in Requirement Coverage InformationReportingFilteringFaultsTest LabTest PlanRequirements


46/50


Limitation in Requirement Coverage Information

Quality Center always shows the last status of

Test Execution

Coverage data of the Requirements show only the result ofthe 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 thelast run of the Test Case in any Test Set




47/50



Req. 2

Req. 1

Requirements

Test Case. 3

Test Case. 1

Test Plan

Test Case. 2

Test Set. 3

Test Set. 1

Test Lab

Test Set. 2

Test Case. 1

Test Case. 2

Test Case. 1

Test Case. 2

Test Case. 3

Test Case. 3

Pass

Pass

Prod. 1

Prod. 2

Prod. 1

Prod. 2

Pass

Pass

Pass

Pass

Pass

Prod. 3

Pass

Req. 3

Prod. 3




48/50



Req. 1

Requirements

Test Case. 1

Test Plan

Test Case. 2

Test Set. 3

Test Set. 1

Test Lab

Test Set. 2

Test Case. 1

Test Case. 2

Test Case. 1

Test Case. 2

Test Case. 3

Test Case. 3

Pass

Pass

Prod. 1

Prod. 1

Prod. 2

Pass

Pass

Pass

Pass

Prod. 3

Pass

Fail

Fail

Fail

FailReq. 2 Test Case. 3

Prod. 2 Pass

Pass

Req. 3

Prod. 3

Fail

Fail

FailFail

Questions?


49/50


Questions?


50/50

Quality CenterBasic Training

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

Documents

03_Quality Center Functionality and Features