8/8/2019 Doc001 QC Introduction

1/21

1 Introduction

1.1 Purpose

The purpose of this document is to a described an end to end flow of Quality Centre.

1.2 Scope

This is introductory document and therefore the scope of this document to describe the all module of Quality

Centre

Requirement Management: This topic would cover the best practices regarding how to manage theRequirements in QC.

Test Case Management:This topic would cover the best practices regarding the test case standards that weare employing to write test cases more effectively.

Defect Management:This topic would cover that how to manage defects in Quality Center.

Quality Center Features:Here, we will look at some of the features that we can be utilized for achieving better

results.

2 Requirement Management

2.1 How to create Requirements in Quality Centre

i) Click on the Requirement tab displayed at left pane

ii) Click on New Requirement button to create New Requirement:

a)The Field names and Type under the Details tab can be customised as per project requirement.

b) Enter the fields values under the details Tab.

c)Enter the Project Details Under the Description tab and click on Submit Button

8/8/2019 Doc001 QC Introduction

2/21

Fields Detail of the New Requirement Pane: Fields with * sign are mandatory , But administrator can

customize (Modification, Addition, Deletion) the fields Name and Type according to the Project.

Name: Enter the Requirement Name

Priority: Select from the drop down like Low, Medium etc., its again as per Project.

Product: Select from the drop down on which we are working on, the drop down values can be customized asper Project.

Type: The type of the requirement, select from the Drop down like Functional, system etc.

Creation date: system will take auto values.

Creation Time: System will take auto values.

Direct Cover Status: By default its appeared Not Covered as initially Test Cases are not mapped with therequirement.

Modified: System will take auto values.

Planned Version: Select the value from the drop down.

Reviewed: By default the value will appear not reviewed, other values can be selected from the drop down.

Reviewer: Select the the name of the reviewer from the drop down.

Description: Enter the Requirement data in this field, but more fields can be added if required.

2.2 How to Create Child Requirement:

i) Click on New Child Requirement to Create New Child Requirement:

8/8/2019 Doc001 QC Introduction

3/21

ii) Enter the fields value into the details pane.

Iii) Enter the requirement data into the description area and click on submit button.

2.3 Created Requirements in Quality Centre

Various tab details are as follows:

Test Coverage tab: This tab is used to seethe Test cases covered under this requirement.

Details tab: This tab is used to enter all the details regarding the project requirement.

Attachment Tab: This tab is used to attach any document regarding this particular Requirement.

Linked defects: This tab is used to see the linked defects with this particular requirement.

2.4 Requirement Mapping with Test cases

8/8/2019 Doc001 QC Introduction

4/21

i) Click on Requirement Tab and select the requirement from section A.

ii) Click on Test Coverage tab in the section B.

iii)Go to the section C and select the Test Cases which needs to be mapped with the selected requirement.

iv) Click on highlighted arrow button in the section C, the selected Test cases will be mapped with requirementand this will be appeared in the highlighted area ofsection B.

Note: The sections A,B & C are are not the part of the QC, these are written to explain thefunctionality.

2.5 How to See Requirement Coverage

i) Click on Requirement Tab from the Left Pane.ii) Click on View Button from the Top Bar and select the Coverage Analysis View.

Iii) Click on the highlighted area NO Run under the Direct Cover Status Column.

8/8/2019 Doc001 QC Introduction

5/21

iv) The coverage analysis window will be displayed.

v) Click on the Show Tests Coverage Link (which is now showing after click as Hide Tests coverage), the Tests

Coverage Pie Chart will be displayed, which is showing status 2 No Run Test Cases.

2.6 End to End flow of Requirement Coverage

3. Test case Management

8/8/2019 Doc001 QC Introduction

6/21

3.1 Elements of Effective test cases:

i) Purpose Drivena) Tied to Requirements or Use Cases.

b) Covers all aspects of testing.

ii) Uniform Structure

iii) Uniform Standards

iv) Reusable Features

3.1.1 Uniform structure

i) Project Description

ii) Project Attachment

iii) Test Case Naming Standards

iv) Details tab

Purpose Pre - ConditionsPost - Conditions

Data information

Attachments

Called test cases (if any)

Owner

Priority

Attachment tab

Requirement Coverage tab

3.1.1.1 Project Description:

How to write a Project description

i)Click on Test Plan Tab, Highlight the folder and enter the following:

Description Tab: Enter the Project details under the Description Tab.

Attachments tab: Multiple Reference Documents can be attached under the attachment tab.

Live Analysis: Graphical representation of data can be put under this Tab.

8/8/2019 Doc001 QC Introduction

7/21

ii) Enter the Test Set specific details in sub folders

3.1.1.2 Project Attachment tab

Attach the project related documents under Attachment tab and write the attachment details into the DescriptionTab.

8/8/2019 Doc001 QC Introduction

8/21

3.1.1.3 Test case Naming Standards

i) Test case name should be self explanatory

ii) User should be able to identify test case with requirement document.

Iii) Following naming sample can be used:

__< scenario_name>

3.1.1.4 Details Tab

Enter the Test case details into the Details tab.

Enter the following information of the Test case:

Purpose: This explains the objective for which the test case has been created.

Validation Points: This lists the various criteria that need to be validated in order to achieve a successful

8/8/2019 Doc001 QC Introduction

9/21

execution.

Attachments: This provides information about the various attachments uploaded along with the test case.

Pre Conditions:This lays out the various preconditions that need to be fulfilled in order to start execution ofthis test case.

Post Conditions: This lists the state of the application after the successful execution of test case is done.Test Case Called: Write the name of the Test Case called if any.

3.1.1.5 Attachment Tab

Click on the Attachment tab , Upload the required documents using the highlighted button and Enter therequired information under description.

3.2 Requirement coverage

The requirement coverage feature provides the user an easy way to track the coverage of theproject requirements by various test cases. It allows the author of test case to map each andevery one of the test case to the appropriate requirement. Thus it provides kind of a traceabilitymatrix between requirement and test case.The below snapshot is displayed the requirement coverage of the particular Test case.

8/8/2019 Doc001 QC Introduction

10/21

3.2.1 How a test case is mapped to the Requirement

i) Select the Select req button (Highlighted button)

ii) The requirements are displayed on the right pane.

Iii) Browse through the requirements and select the requirement pertaining to the test case.

This may be a scenario that One test set is mapped with Multiple requirements.

iv) Click on the right arrow button displayed at the top of requirement window. The specific requirement isdisplayed under entity name with its appropriate description.

v) Click on the refreshed button.

Requirement is mapped to the test case.

8/8/2019 Doc001 QC Introduction

11/21

3.3Uniform Standards for writing a Test case

Bold: Bold the name of screens and links to emphasize on their importance.

Bullets/Numbers: Use bullets/Numbers to present the menu structures or any other serialized information

Colors: Use different colors to identify the description and expected results.

Document every Step: Document each and every step in order to depict the smooth

navigation flow and facilitate the user friendliness.

4 Defect Management

4.1Logging a New Defect

i) Click on Defects tab at left pane

8/8/2019 Doc001 QC Introduction

12/21

ii) Click on New Defect button. New Defect window will appear.

Summary: Enter the Summary of the defect. This summary should be crystal clear so that eachindividual will be able to understand the defect by reading the Summary only.

Category: This will define the Category of the Defect like Functional, UI etc. Subject: You can select the Test Set from this field where defect exist. Detected By: This field should be filled with the name of the person who had detected this defect. Detected on Date: This date field will be populated automatically by QC itself. Project: Select the project for which you are logging a defect. Detected in Version: Select the Version of build. Severity: Set the Severity of the Defect. Status: This will display the status of the defect. By default, it will be new at the first time. Reproducible: This field will display that Defect is reproducible or not.

Description: Write down each and every step to reproduce the Defect. Provide the Test Data for whichDefect is detected.

Note: Above described fields can be customized according to need of project.

Enter all the Information for the Defect and click on Submit button.

8/8/2019 Doc001 QC Introduction

13/21

4.2 Verify the newly Logged Defect.

i) Open the newly logged defect by double clicking it.

8/8/2019 Doc001 QC Introduction

14/21

4.3Link a Defect with the Failed Test case

i) Click Test Lab tab and select Failed Test Case

ii) Click to link an already existing defect

8/8/2019 Doc001 QC Introduction

15/21

iii) Defect is linked to the test case

iv) Verify the linked defect on Defect Tab by opening the defect and click Others tab .

8/8/2019 Doc001 QC Introduction

16/21

5 Quality Centre Features:This section describe the Reusable features of Quality Centre

i) Modular:

The idea is to make script more independent so that the same can be used across different platforms, differentprojects etc.

For example : Parameterization

ii) Reuse:

Some common scripts can be made as templates and then used across different scripts and projects leading toincrease in efficiency.

For example: Call to test

5.1 Parameterization: Parameterization is a process by means of which user can introduce the Dynamicconcept in the script. It enables the user to enter the values of standard fields like url, username, name etc. atthe runtime. Thus it makes script modular and hence enables user to utilize the same script during execution ofsome other project.In the below snapshot,Highlighted are the parameterized fields.

8/8/2019 Doc001 QC Introduction

17/21

5.1.1 How to Parameterize a field:

i) Place the cursor near the field user wants to parameterize.e.g. In attached screen shot, user wants toparameterize First name, hence cursor is placed near the field.

ii) Click on the highlighted button.

Iii) Parameter properties window is invoked. Enter the Parameter name.

iv) Click on the OK button.

8/8/2019 Doc001 QC Introduction

18/21

The required field is parameterized. Thus, the script can be reused as it does not hard code the value offirstname in the script

5.2 Call to Test

5.2.1 How to make a Test case as Template

i)Select the required test.

ii)Select Mark as Template Test from the menu.

8/8/2019 Doc001 QC Introduction

19/21

Iii) Test case Icon will change for Template.

8/8/2019 Doc001 QC Introduction

20/21

5.2.2 How to Call a Template

i) Select the test in which this template needs to be included.

ii)Highlight the test step where the template needs to be embedded.Iii) Click on the call to test button. (Highlighted button)

iv) Select the template that needs to be embedded.v) Select Show only Template tests check box.

8/8/2019 Doc001 QC Introduction

21/21

The embedded template is displayed in the design steps.