Business Component

You can define testing process by specifying releases in Releases Module. A release represents one or more applications that will be available for distribution at the same time. Each release can contain a number of cycles. A cycle represents a development or QA cycle based on the project timeline. Release and cycles have defined start and end date.

To define the releases and cycles, follow the below steps.

Steps to define Release

1. Open the Project
2. Click on "Releases" button on the side bar.
3. In releases tree, select the Root releases folder. Click the New Release folder button.
Enter the name of the release folder and click on OK.
4. Select the folder that is created and click on "New Release" button
5. In the "Release Name" box, enter the name of the release and click on "Ok"

Steps to define new cycle

1. Select the Release
2. Click the New Cycle button
3. In the "Cycle Name" box, enter the name of the cycle and click on "OK"

Progress Graph for the Release In the release tree, select the release located in the release folder. In the right pane, click on progress tab. In the progress tab displays the progress of the release based on the requirement coverage, elapsed and remaining time, actual and remaining test instances to run.

Quality Graph for the Release
In the release tree, select the release located in the release folder. In the right pane, click on Quality tab.

Defects Opening Graph for the Release
This graph summarizes the number of defects detected in the selected release

Outstanding Defect Graph for the Release
This graph summarizes the number of outstanding defects for the selected release

Program Graph and Quality Graph for the Cycle In the release tree, select the cycle located in the release. In the right pane, click on Progress tab.

Requirements

Requirements describe in detail what needs to be tested in your application and provide the test team with the foundation on which the entire test process is based.

You define Requirements by building Requirements Tree. This is a graphical representation of your requirement specification, defining your requirements hierarchically.

Requirement Specification Module helps in:
1. Grouping and sorting requirement in a tree
2. monitoring the task allocation
3. monitoring the progress in meeting requirements
4. generating detailed graphs and reports.

Major tasks under Requirement Specification Module are
1. Defining Requirements
2. Viewing Requirements
3. Modifying Requirements
4. Converting Requirements

To define requirements, you need to follow the following steps
1. Open the project
2. Click on requirements button on the side bar

Create a New Requirement
1. Select the root requirement and click on "New Requirement" button

Test Plan

This module is used for designing the Test Cases and to store the Test Scripts.

Test Cases can be mapped with requirements, which are created. Each Requirement can be mapped with one or more test Case.

Test Lab

This module is used for executing the Test Cases and Track the Results.

1. Building the Test Set
2. Execute the Test Set
3. Analyse the Results

Defects:
This module acts like a Bug Tracking Tool. It helps in Managing the Defects like, adding a defect, changing the status of the defect.

Dashboard

This module enables you to define graphs and reports.

ReportYou can generate a report from Requirements, Test Plan, Test Lab and Defects.

Execution Report:enables project Manager to see a list of test instances and results.

Graph:To Generate the graph Choose Analysis > Graph > Group-Summary by Status

Live Analysis Graph:Provides a visual overview of all the tests within the folder in Test Plan Tree.

Summary Graph:Enables to view the child requirements data related to the tests that the requirements cover

Coverage Progress Graph:

Defect Opening Rate Graph: Summarizes the number of defects detected in the selected release.

Outstanding Defects: Summarizes the number of outstanding defects in the selected release. By default, defects with the status of New, Open and ReOpen are displayed in the Graph.

Introduction

QC is developed by Mercury Interactive Owned by HP Presently.

Quality Center is a Web Based Test Management Tool. QC is formally known as Test Director.

Quality Center provides:
1. Common Repository
2. Automatic Traceability Matrix
3. Bug Tracking Facility
4. Automatic Reports and Graph Generator

The following activities can be managed or organized using Quality Center:
1. Requirements Coverage
2. Test Case Management
3. Test Execution Reporting
4. Defect Management
5. Test Automation

Quality Center can be divided into parts:
1. Site Administrator Bin
2. Quality Center Bin

Site Administrator Bin: This part is used for all the administrative activities. From this part of the Quality Center, we generally do the following activities.
- Creating the projects
- Assigning users to the projects
- Creating specific roles
- Configuring QTP or Win Runner Scripts
- Verifying licencing information
- Information about Database

Quality Center Bin: This part is used by testers or test manager. From this part of Quality Center, we generally do the following activities.
- Defining Requirements
- Creating Test Plan
- Creating Test Cases
- Creating Test Lab
- Creating Defects

Microsoft Quality Center is installed as a service in Microsoft Windows Environment. Before Start working on it, make sure that microsoft quality center service is running.

Microsoft Quality Center provide role based access to the projects. For example, Test Manager can create a project, Test Lead can create test plan and tester can write test cases.

Quality Center can be divided in to 6 sections:
1. Business Component
2. Requirements
3. Test Plan
4. Test Lab
5. Defects
6. Dash Board